CVE-2026-27723: CWE-284: Improper Access Control in opf openproject
OpenProject is an open-source, web-based project management software. Prior to versions 17.0.5 and 17.1.2, an attacker can create wiki pages belonging to unpermitted projects through an improperly authenticated request. This issue has been patched in versions 17.0.5 and 17.1.2.
AI Analysis
Technical Summary
CVE-2026-27723 is classified under CWE-284 (Improper Access Control) and affects OpenProject, a widely used open-source project management software. The vulnerability arises from insufficient authentication checks that allow an attacker with some level of authenticated access (PR:L - privileges required) to create wiki pages in projects for which they lack explicit permissions. This improper access control flaw enables unauthorized data modification, specifically the creation of wiki content in unpermitted projects. The vulnerability does not impact confidentiality or availability but compromises data integrity by allowing unauthorized content injection. The CVSS v3.1 score is 4.3 (medium), reflecting that the attack vector is network-based (AV:N), requires low attack complexity (AC:L), privileges (PR:L), no user interaction (UI:N), and has unchanged scope (S:U). The issue was addressed in OpenProject versions 17.0.5 and 17.1.2 by enforcing stricter permission checks on wiki page creation requests. No public exploits have been reported, indicating limited active exploitation. However, the vulnerability poses a risk to organizations relying on OpenProject for collaborative documentation and project tracking, as unauthorized wiki pages could mislead teams or disrupt project integrity.
Potential Impact
The primary impact of CVE-2026-27723 is the unauthorized modification of project documentation through the creation of wiki pages in projects where the attacker lacks permission. This can lead to misinformation, confusion, and potential disruption of project workflows, undermining trust in project data integrity. While confidentiality and availability remain unaffected, the integrity compromise can have cascading effects on decision-making and project outcomes. Organizations using vulnerable OpenProject versions may face risks of insider threats or compromised accounts being leveraged to inject misleading or malicious content. This can be particularly damaging in environments where project documentation is critical for compliance, auditing, or operational continuity. The lack of known exploits reduces immediate risk, but the ease of exploitation (low complexity, network accessible) means that attackers could develop exploits if motivated. Overall, the threat could impact project management efficiency and organizational trust in collaborative tools.
Mitigation Recommendations
To mitigate CVE-2026-27723, organizations should promptly upgrade OpenProject installations to versions 17.0.5 or 17.1.2 or later, where the vulnerability has been patched. Beyond patching, administrators should audit user roles and permissions to ensure that only authorized users have access to create or modify wiki pages within projects. Implementing strict role-based access control (RBAC) policies and regularly reviewing permission assignments can reduce the risk of privilege misuse. Monitoring logs for unusual wiki page creation activity can help detect potential exploitation attempts. Additionally, consider deploying web application firewalls (WAFs) with custom rules to detect and block unauthorized API requests related to wiki page creation. Educating users about the importance of account security and enforcing strong authentication mechanisms (e.g., MFA) can further reduce the risk of compromised credentials being used to exploit this vulnerability.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Netherlands, Sweden, Switzerland, Japan
CVE-2026-27723: CWE-284: Improper Access Control in opf openproject
Description
OpenProject is an open-source, web-based project management software. Prior to versions 17.0.5 and 17.1.2, an attacker can create wiki pages belonging to unpermitted projects through an improperly authenticated request. This issue has been patched in versions 17.0.5 and 17.1.2.
AI-Powered Analysis
Technical Analysis
CVE-2026-27723 is classified under CWE-284 (Improper Access Control) and affects OpenProject, a widely used open-source project management software. The vulnerability arises from insufficient authentication checks that allow an attacker with some level of authenticated access (PR:L - privileges required) to create wiki pages in projects for which they lack explicit permissions. This improper access control flaw enables unauthorized data modification, specifically the creation of wiki content in unpermitted projects. The vulnerability does not impact confidentiality or availability but compromises data integrity by allowing unauthorized content injection. The CVSS v3.1 score is 4.3 (medium), reflecting that the attack vector is network-based (AV:N), requires low attack complexity (AC:L), privileges (PR:L), no user interaction (UI:N), and has unchanged scope (S:U). The issue was addressed in OpenProject versions 17.0.5 and 17.1.2 by enforcing stricter permission checks on wiki page creation requests. No public exploits have been reported, indicating limited active exploitation. However, the vulnerability poses a risk to organizations relying on OpenProject for collaborative documentation and project tracking, as unauthorized wiki pages could mislead teams or disrupt project integrity.
Potential Impact
The primary impact of CVE-2026-27723 is the unauthorized modification of project documentation through the creation of wiki pages in projects where the attacker lacks permission. This can lead to misinformation, confusion, and potential disruption of project workflows, undermining trust in project data integrity. While confidentiality and availability remain unaffected, the integrity compromise can have cascading effects on decision-making and project outcomes. Organizations using vulnerable OpenProject versions may face risks of insider threats or compromised accounts being leveraged to inject misleading or malicious content. This can be particularly damaging in environments where project documentation is critical for compliance, auditing, or operational continuity. The lack of known exploits reduces immediate risk, but the ease of exploitation (low complexity, network accessible) means that attackers could develop exploits if motivated. Overall, the threat could impact project management efficiency and organizational trust in collaborative tools.
Mitigation Recommendations
To mitigate CVE-2026-27723, organizations should promptly upgrade OpenProject installations to versions 17.0.5 or 17.1.2 or later, where the vulnerability has been patched. Beyond patching, administrators should audit user roles and permissions to ensure that only authorized users have access to create or modify wiki pages within projects. Implementing strict role-based access control (RBAC) policies and regularly reviewing permission assignments can reduce the risk of privilege misuse. Monitoring logs for unusual wiki page creation activity can help detect potential exploitation attempts. Additionally, consider deploying web application firewalls (WAFs) with custom rules to detect and block unauthorized API requests related to wiki page creation. Educating users about the importance of account security and enforcing strong authentication mechanisms (e.g., MFA) can further reduce the risk of compromised credentials being used to exploit this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-23T18:37:14.789Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69a9c996460e1c85df13935c
Added to database: 3/5/2026, 6:21:10 PM
Last enriched: 3/5/2026, 6:36:03 PM
Last updated: 3/5/2026, 9:05:00 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.