Skip to main content

OpenProject CVE-2026-47193

| EUVDEUVD-2026-39872 HIGH
Information Exposure (CWE-200)
2026-06-26 GitHub_M
7.5
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate or reach OpenProject instance
  2. Delivery
    Request journal diff for restricted work package
  3. Exploit
    Endpoint skips object/field visibility checks
  4. Execution
    Hidden historical field values returned
  5. Impact
    Sensitive data disclosed

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires reaching the journal diff (work-package change-history) endpoint and requesting the diff for an object or field the requester is not authorized to view; the bug is that the endpoint does not re-enforce object and field visibility, so restricted historical values are returned. The CVSS vector states PR:N/UI:N (no privileges or user interaction), but a journal/history endpoint is normally accessible only within an authenticated session, so realistically a logged-in account on the instance is the limiting factor - verify auth requirement against the GHSA advisory. Limiting factors: the target must run a version prior to 17.3.3 or 17.4.1, the instance must be network-reachable to the attacker, and impact is confined to confidentiality (no data modification or service disruption). Authentication requirements are not fully confirmed from the available data because the CVSS PR:N appears inconsistent with the endpoint's nature.

Impact

The vendor-provided CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N = 7.5) models a network-reachable, low-complexity, no-interaction, unauthenticated read with high confidentiality and no integrity or availability impact, which is internally consistent for a pure data-disclosure bug. However, PR:N conflicts with the typical reality of a journal/history endpoint, which is usually reachable only by an authenticated session - the disclosure is about bypassing field/object visibility rather than bypassing login - so the practical privilege requirement is likely PR:L; verify with the GHSA advisory. No EPSS score, KEV entry, POC, or SSVC decision data was supplied, so exploitation probability cannot be quantified from the input. Treating it as an authenticated information-disclosure issue, real-world risk is moderate: it leaks data but grants no code execution or modification. Prioritize patching on internet-exposed or multi-tenant instances where confidentiality of work-package history matters.

Exploit ScenarioDerived

An attacker with access to an OpenProject instance requests the journal/history diff for a work package whose fields or related objects they are not authorized to see. Because the diff endpoint omits the visibility checks, the response returns the hidden historical values - for example previously redacted custom-field contents or restricted descriptions - disclosing data the attacker could not view through the normal UI. No public POC is currently identified, and exploitation needs only a crafted request, consistent with the low attack complexity.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 26, 2026

Information disclosure in OpenProject before 17.3.3 and 17.4.1 lets remote attackers read hidden historical field values through the journal diff endpoint, which fails to enforce object- and field-level visibility checks. The flaw (CWE-200) carries a CVSS 7.5 driven entirely by high confidentiality impact, exposing prior values of work-package fields that should be restricted. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.

RemediationAI

Vendor-released patch: upgrade to OpenProject 17.3.3 (for 17.3.x deployments) or 17.4.1 (for 17.4.x deployments) per advisory GHSA-f2rx-x2qj-2hgj (https://github.com/opf/openproject/security/advisories/GHSA-f2rx-x2qj-2hgj). If immediate upgrade is not possible, restrict network reachability of the OpenProject instance - place it behind a VPN or IP allowlist and ensure it is not exposed to untrusted users - and tighten project/work-package membership so fewer accounts have access to sensitive work packages, accepting that this only narrows the audience rather than closing the disclosure. As a stopgap you can also block or proxy-filter requests to the journal diff/history endpoint at a reverse proxy, with the side effect of breaking legitimate change-history views for all users; this is a usability trade-off and not a substitute for the patch.

Affected VersionsENISA

openproject < 17.3.3
openproject 17.4.0, < 17.4.1

Affected Packages

euvd openproject fix: 17.3.3, 17.4.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OpenProject (CPE cpe:2.3:a:opf:openproject) is a Ruby on Rails web-based project and work-package management platform that records every change to a work package as a 'journal' entry, enabling an audit/history diff view. The journal diff endpoint computes and returns the before/after values of changed fields. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): the diff rendering path does not re-apply the same object visibility and per-field permission filters that the normal work-package views enforce, so historical values of restricted objects or fields are serialized into the diff response regardless of the requester's authorization.

Know when Openproject gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable history endpoint with low complexity; a journal/diff view normally needs an authenticated session, so PR:L; pure confidentiality disclosure means C:H, I:N, A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

1
Patch available
Jun 26, 2026 - 21:02 EUVD

DescriptionCVE.org

OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, the journal diff endpoint discloses hidden historical field values without enforcing object and field visibility. This vulnerability is fixed in 17.3.3 and 17.4.1.

Executive ViewAI

Why It Matters

OpenProject installations running versions before 17.3.3 and 17.4.1 expose a data disclosure vulnerability enabling remote access to restricted work-package field history, potentially revealing confidential project modifications and prior values that should remain hidden. Organizations risk unauthorized visibility into sensitive project data with compliance and competitive intelligence implications.

Business Impact: High
Compensating Controls

Restrict network access to OpenProject journal diff API endpoints to trusted networks only; implement role-based access controls limiting endpoint access to administrators; enable comprehensive audit logging of all endpoint requests; disable the endpoint if operationally feasible; conduct quarterly reviews of work-package visibility rules and access patterns for anomalies.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Medium
popular open-source project management tool, common but not ubiquitous
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2019-11600 HIGH POC
8.1 May 13

A SQL injection vulnerability in the activities API in OpenProject before 8.3.2 allows a remote attacker to execute arbi

CVE-2023-33960 HIGH POC
7.5 Jun 01

OpenProject is web-based project management software. Rated high severity (CVSS 7.5), this vulnerability is remotely exp

CVE-2023-31140 MEDIUM POC
6.5 May 08

OpenProject is open source project management software. Rated medium severity (CVSS 6.5), this vulnerability is remotely

CVE-2026-46386 CRITICAL
9.9 Jun 26

Authenticated remote code execution affects the official openproject/openproject Docker image, which ships with a hardco

CVE-2026-52782 CRITICAL
9.9 Jun 26

Cross-project folder hijacking in OpenProject before 17.3.3 and 17.4.1 lets a project-admin abuse an insecure direct obj

CVE-2026-52785 CRITICAL
9.9 Jun 26

SQL injection in OpenProject's baseline-comparison (timestamps) functionality lets an authenticated, low-privileged user

CVE-2026-25763 CRITICAL POC
9.9 Feb 06

OpenProject has a CVSS 9.9 command injection vulnerability allowing authenticated users to execute OS commands on the pr

CVE-2026-52780 CRITICAL
9.6 Jun 26

Remote code execution in OpenProject before 17.3.3 and 17.4.1 arises from cache store poisoning, allowing an attacker wi

CVE-2026-32698 CRITICAL
9.1 Mar 18

OpenProject, a web-based project management platform, contains a critical SQL injection vulnerability in versions prior

CVE-2026-22600 CRITICAL
9.1 Jan 10

OpenProject (before 16.6.4) has a local file read vulnerability through SVG-based ImageMagick exploitation in the PDF ex

CVE-2026-32703 CRITICAL
9.0 Mar 18

OpenProject's Repositories module contains a stored cross-site scripting (XSS) vulnerability that occurs when displaying

CVE-2026-24772 HIGH
8.9 Jan 28

Token decryption in OpenProject 17.0 allows authenticated attackers to intercept and decrypt 24-hour authentication toke

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy