Skip to main content
VulnerabilityPublished

CVE-2026-24775: opf openproject · Insufficient Verification of Data Authenticity

Affects opf openprojectSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium : upgrade to 17.0.2 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.0.2, 0.0.22
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade openproject to 17.0.2; opf/op-blocknote-extensions to 0.0.22.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • >=17.0.0 <17.0.2
Fixed in
  • 17.0.2
GitHubopf/op-blocknote-extensionspkg:github/opf/op-blocknote-extensionsOther threatsAffected
  • <0.0.22
Fixed in
  • 0.0.22

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade OpenProject to version 17.0.2 or later, which includes the patched op-blocknote-extensions 0.0.22 with proper input validation.
  2. If immediate upgrading is not feasible, disable the collaborative document editing feature by navigating to Settings -> Documents -> Real time collaboration and selecting Disable.
  3. Implement strict access controls to limit who can create or edit collaborative documents, reducing the risk of malicious document creation.
  4. Educate users to be cautious when opening documents from untrusted sources within OpenProject.
  5. Monitor OpenProject API logs for unusual GET requests or patterns indicative of exploitation attempts.
  6. Consider network segmentation or application-layer firewalls to restrict internal API access where possible.
  7. Regularly audit OpenProject instances for version compliance and configuration to ensure timely application of security patches.

Description

OpenProject is an open-source, web-based project management software. In the new editor for collaborative documents based on BlockNote, OpenProject maintainers added a custom extension in OpenProject version 17.0.0 that allows to mention OpenProject work packages in the document. To show work package details, the editor loads details about the work package via the OpenProject API. For this API call, the extension to the BlockNote editor did not properly validate the given work package ID to be only a number. This allowed an attacker to generate a document with relative links that upon opening could make arbitrary `GET` requests to any URL within the OpenProject instance. This issue was patched in version version 0.0.22 of op-blocknote-extensions, which was shipped with OpenProject 17.0.2. If users cannot update immediately to version 17.0.2 of OpenProject, administrators can disable collaborative document editing in Settings -> Documents -> Real time collaboration -> Disable.

References

Community reviews

Loading reviews…