CVE-2026-52780
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, cache store poisoning leads to Remote Code Execution (RCE). This vulnerability is fixed in 17.3.3 and 17.4.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenProject versions prior to 17.3.3 and 17.4.1 contain a cache store poisoning vulnerability that can be exploited to achieve remote code execution. An attacker with the ability to manipulate the cache store can inject malicious data that gets deserialized or executed by the application, leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OpenProject versionRun the command to display the OpenProject version, typically via the application admin interface, CLI tool, or by checking the installed package version on the systemAffected if The version displayed is lower than 17.3.3 or 17.4.1 (e.g., 17.3.0, 17.2.x, earlier major versions)
-
Determine the cache store configurationLocate and inspect the OpenProject configuration file that defines the cache store backend (commonly config/caches.yml or similar configuration mechanism)Affected if A cache store is configured and in use by the application
-
Check if cache store is externally accessibleReview network access controls and cache store configuration to determine if an attacker could inject or manipulate cached dataAffected if The cache store accepts external input or is accessible to untrusted users who could poison cached data
If the installed OpenProject version is prior to 17.3.3 or 17.4.1 and uses a cache store that can be manipulated, the environment is vulnerable to cache store poisoning leading to potential remote code execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade OpenProject to version 17.3.3 or 17.4.1 or later to remediate this vulnerability. Given the critical severity and RCE potential, prioritize patching immediately.
17.3.3 or 17.4.1 (recommended: 17.4.1)
- 1. Check the current installed version of OpenProject (e.g., via command line or admin interface)
- 2. Back up the OpenProject database and all configuration files before upgrading
- 3. Stop the OpenProject service
- 4. Follow the official upgrade instructions for your deployment method (Docker, package, or source) to upgrade to version 17.3.3 or 17.4.1
- 5. Start the OpenProject service
- 6. Verify the upgrade was successful by checking the version number in the admin interface
- 7. Test critical functionality to ensure the upgrade did not break existing workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data