CVE-2026-25531 in Kanboardinfo

Summary

by MITRE • 02/13/2026

Kanboard is project management software focused on Kanban methodology. Prior to 1.2.50, The fix for CVE-2023-33968 is incomplete. The TaskCreationController::duplicateProjects() endpoint does not validate user permissions for target projects, allowing authenticated users to duplicate tasks into projects they cannot access. This vulnerability is fixed in 1.2.50.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 02/13/2026

The vulnerability identified as CVE-2026-25531 affects Kanboard project management software, a tool specifically designed around the Kanban methodology for workflow management. This issue represents a regression in security controls that were initially addressed in a previous vulnerability fix, specifically CVE-2023-33968. The vulnerability exists within the TaskCreationController::duplicateProjects() endpoint, which handles the functionality for duplicating tasks between projects. The flaw demonstrates a critical breakdown in the application's access control mechanisms that undermines the fundamental security model of the software.

The technical implementation of this vulnerability stems from incomplete validation of user permissions within the duplicateProjects() method. When authenticated users attempt to duplicate tasks into target projects, the system fails to properly verify whether the requesting user possesses appropriate access rights to the destination project. This permission bypass allows malicious or unauthorized users to move task data between projects where they should not have access, effectively creating a privilege escalation scenario. The vulnerability specifically targets the authorization controls that should prevent users from manipulating data in projects outside their designated scope, representing a clear violation of the principle of least privilege.

The operational impact of this vulnerability extends beyond simple data integrity concerns, as it enables unauthorized data movement that could compromise project confidentiality and workflow management. An attacker with valid authentication credentials could exploit this flaw to place sensitive task information into projects accessible only to specific team members or stakeholders. This capability undermines the collaborative security model of Kanboard, where different projects typically represent different security domains or business units. The vulnerability essentially allows for unauthorized data propagation across project boundaries, potentially exposing confidential project information to users who should not have access to such data.

Security professionals should note that this vulnerability aligns with CWE-285, which addresses improper authorization issues in software systems. The flaw represents a classic case of insufficient access control validation that could be exploited as part of broader attack vectors. From an ATT&CK framework perspective, this vulnerability could be leveraged in the privilege escalation and defense evasion phases, allowing threat actors to move laterally within project management environments. Organizations using Kanboard should prioritize immediate patching to version 1.2.50, which contains the complete fix for this permission validation issue. The remediation process should include comprehensive testing of project access controls and user permission configurations to ensure no residual vulnerabilities exist in the system's authorization framework.

The vulnerability demonstrates the importance of thorough regression testing in security patches, as the initial fix for CVE-2023-33968 was incomplete in addressing all potential attack vectors within the same code module. This oversight highlights the need for comprehensive security reviews of related functionality when implementing fixes for similar vulnerabilities. The issue also underscores the critical nature of maintaining proper access controls in collaborative software environments where multiple users interact with shared project data, emphasizing that even authenticated users must be properly validated before being granted access to specific project resources. Organizations should implement monitoring and logging around task duplication activities to detect potential unauthorized access attempts and maintain audit trails for security incident response purposes.

Responsible

GitHub M

Reservation

02/02/2026

Disclosure

02/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00037

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!