Skip to main content
VulnerabilityPublished

CVE-2026-52784: opf openproject · Cross-Site Request Forgery (CSRF)

Affects opf openprojectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 17.4.1 or 17.3.3 soon.

Data as of 8 Nov 2026, 23:24 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 8 Nov 2026.

What to do

Upgrade openproject and opf/openproject to 17.4.1 or 17.3.3.

Affected software

ProductAffectedFixed in
opfopenprojectAffected
  • >=17.4.0 <17.4.1
Fixed in
  • 17.4.1
opfopenprojectAffected
  • <17.3.3
Fixed in
  • 17.3.3
GitHubopf/openprojectpkg:github/opf/openprojectOther threatsAffected
  • <17.3.3
  • <17.4.1
Fixed in
  • 17.3.3
  • 17.4.1

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

AI-suggested

Upgrade OpenProject to version 17.3.3 or 17.4.1 or later, where this CSRF vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data.

Description

OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is a CSRF on TARGET through /users/:id via POST parameter "user[admin]". This vulnerability is fixed in 17.3.3 and 17.4.1.

References

Community reviews

Loading reviews…