Security readout for executives and security teams
Plain-English summary
OpenProject 17.0.0 through before 17.0.2 has a document editor flaw. A user-created collaborative document can trigger unwanted internal GET requests inside the same OpenProject instance when another user opens it. The main business risk is disruption of availability, with limited integrity impact. The vendor shipped a fix in OpenProject 17.0.2.
Executive priority
Treat as a near-term patching item for affected OpenProject 17.0.x deployments. Prioritize systems with broad user access or heavy collaborative document use. The issue is not described as remotely unauthenticated or actively exploited in the provided sources.
Technical view
The vulnerable op-blocknote-extensions work package mention feature failed to validate that a work package ID was numeric. A low-privileged attacker could craft a document containing relative links that cause arbitrary GET requests within the OpenProject instance when opened. CVSS is 6.3: network attack vector, low complexity, privileges required, and user interaction required.
Likely exposure
Exposure appears limited to OpenProject deployments running versions >= 17.0.0 and < 17.0.2 with collaborative document editing enabled. The issue requires an authenticated attacker and a victim opening the crafted collaborative document.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires privileges to create or modify a collaborative document and user interaction from another user. Impact includes forced actions, content spoofing, and potentially persistent denial of service within OpenProject.
Researcher notes
Root cause is improper validation of a work package ID in the BlockNote editor extension. Scope is same OpenProject instance via relative URLs. Avoid assuming impact beyond GET requests and documented availability/integrity effects unless confirmed by vendor analysis.
Mitigation direction
- Upgrade OpenProject to version 17.0.2 or later.
- Confirm op-blocknote-extensions is updated to version 0.0.22 or later.
- If unable to upgrade, disable collaborative document editing in OpenProject settings.
- Monitor vendor advisory updates for any additional guidance.
Validation and detection
- Inventory OpenProject instances and record exact versions.
- Check whether collaborative document editing is enabled.
- Review package or release metadata for op-blocknote-extensions version 0.0.22 or later.
- Review logs for unusual internal GET activity after collaborative documents are opened.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24775 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H2.14.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/opf/openproject/security/advisories/GHSA-35c6-x276-2pvcCVE reference · x_refsource_CONFIRM
- https://github.com/opf/op-blocknote-extensions/releases/tag/v0.0.22CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.