Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-47193 – Unauthenticated Information Disclosure – OpenProject prior to 17.3.3 / 17.4.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-47193 is a high-severity authorization bypass and information disclosure vulnerability in OpenProject, an open-source web-based project management platform. The journal diff endpoint (GET /journals/:journal_id/diff/:field) fails to enforce object-level, journal-level, and field-level visibility controls, allowing unauthorized actors to retrieve hidden historical field values from project records. The vulnerability carries a CVSS v3.1 base score of 7.5 (High) and is exploitable remotely without authentication, making every publicly reachable OpenProject instance a potential target.

Technical details

  • Root cause: The diff action in app/controllers/journals_controller.rb maps authorization to overly broad permissions (e.g., view_work_packages for work-package journals, view_project for project journals, view_meetings for meeting journals) without subsequently enforcing the fine-grained visibility checks that the standard OpenProject API and UI apply.
  • Trigger conditions: An attacker sends a crafted GET /journals/:journal_id/diff/:field request. On instances with public projects, no credentials are required. On instances with private projects, any low-privileged user account is sufficient to bypass field-level restrictions.
  • Attack vector: Network-accessible HTTP/HTTPS endpoint; no local access, authentication, or user interaction required (PR:N, UI:N) in public-project configurations.
  • Disclosed data categories (confirmed in the security advisory):
    • Hidden work-package descriptions and metadata from journals of inaccessible work packages
    • Text custom field histories marked admin-only or otherwise restricted
    • Internal/restricted journal contents hidden from users lacking view_internal_comments
    • Project custom field and comment values concealed from users lacking view_project_attributes
    • Historical meeting agenda notes from cancelled meetings
  • Persistence risk: Historical journal diffs retain previous field values even after sensitive content has been removed from current objects, meaning data believed to be deleted or hidden may still be exposed through this endpoint.
  • Weaknesses: CWE-862 (Missing Authorization) and CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor).
  • No public proof-of-concept has been identified at time of publication.

Affected software

  • OpenProject < 17.3.3 (all versions up to and including 17.3.2)
  • OpenProject ≥ 17.4.0, < 17.4.1 (specifically the 17.4.0 release)

Severity

| Property | Value |
|—|—|
| CVSS v3.1 Base Score | 7.5 (High) |
| Vector String | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Confidentiality Impact | High |
| Integrity / Availability Impact | None |

Mitigation and recommended actions

  • Patch immediately: Upgrade to OpenProject 17.3.3 (for organizations on the 17.3.x branch) or OpenProject 17.4.1 (for organizations on the 17.4.x branch). Both releases were published on June 8, 2026 and contain the complete fix.
  • If immediate patching is not possible: Consider restricting network access to the OpenProject instance at the perimeter (firewall or reverse-proxy rules) to prevent unauthenticated internet access to the journal diff endpoint path (/journals/*/diff/*) until the upgrade can be scheduled.
  • Post-patch review: Administrators should audit any custom fields, internal journals, or project attributes marked as restricted or hidden to assess whether sensitive historical values may have been exposed prior to patching.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge