dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-47193

HIGH · 7.5 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
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.

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 confidence

The journal diff endpoint in OpenProject versions prior to 17.3.3 and 17.4.1 fails to enforce object and field visibility controls, allowing unauthorized disclosure of hidden historical field values that should not be accessible to certain users.

MitigationUpgrade OpenProject to version 17.3.3 or 17.4.1 or later to implement proper visibility enforcement on the journal diff endpoint.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenProject installation version
    Check the installed OpenProject version by running 'openproject --version' or inspecting the Gemfile.lock for the openproject gem version, or looking at the About page in the admin interface
    Affected if The installed version is prior to 17.3.3 or between 17.4.0 and 17.4.0 (i.e., any version below 17.3.3 or below 17.4.1)
  2. Verify journal module is enabled
    In the OpenProject admin interface, navigate to Settings > Modules and confirm that the 'Journals' or 'Activity' module is enabled for any project
    Affected if The journal module is active, as the vulnerability exists on the journal diff endpoint
  3. Confirm presence of custom fields with restricted visibility
    Go to Administration > Custom Fields and list all custom fields. Check which ones have visibility restrictions set to roles other than 'All' or 'System admin'
    Affected if There are custom fields or work package attributes with non-public visibility settings configured
  4. Test journal diff endpoint access
    Access the endpoint /journals/{work_package_id}/diff (or similar path) for a work package that contains fields with restricted visibility, using a user account that should not have access to those hidden fields
    Affected if The endpoint returns diff content showing field values that the user role should not be able to view according to visibility settings

You are affected if running any OpenProject version below 17.3.3 or below 17.4.1 AND the journal module is enabled AND your installation uses custom fields or work packages with visibility restrictions that could be exposed through the journal diff endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenProject to version 17.3.3 or 17.4.1 or later to implement proper visibility enforcement on the journal diff endpoint.

Recommended fix Moderate confidence

17.4.1 (latest fixed release)

  1. 1. Identify current OpenProject version by checking the OpenProject administration interface or running `openproject --version`
  2. 2. If running a version prior to 17.3.3 on the 17.3.x line, plan upgrade to version 17.3.3
  3. 3. If running a version prior to 17.4.1 on the 17.4.x line, plan upgrade to version 17.4.1
  4. 4. Review OpenProject release notes for the target version for any migration requirements
  5. 5. Create a backup of the OpenProject database and configuration
  6. 6. Perform the upgrade following OpenProject's standard upgrade procedure
  7. 7. Verify the upgrade was successful and test the journal diff functionality
Caveat Review OpenProject 17.4.1 release notes for any breaking changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47193 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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