CVE-2026-47193
Deferred Deferred - Pending Action
Information Disclosure in OpenProject Journal Diff

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-06-27
AI Q&A
2026-06-27
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
openproject openproject to 17.3.3 (inc)
openproject openproject to 17.4.1 (inc)
openproject openproject to 17.4.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

This vulnerability allows unauthorized disclosure of hidden historical text values, including sensitive data such as hidden work package descriptions, restricted journal contents, project custom fields, and cancelled meeting notes.

Such unauthorized data exposure could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls on access to sensitive and personal information.

Because the vulnerability bypasses object, journal, and field visibility checks, it undermines the confidentiality and access control measures that are essential for compliance with these standards.

Executive Summary

CVE-2026-47193 is a vulnerability in OpenProject, an open-source web-based project management software. The issue exists in the journal diff endpoint (GET /journals/:journal_id/diff/:field), which bypasses object, journal, and field visibility checks.

This means that unauthorized users, including low-privileged or unauthenticated users in public-project configurations, can access hidden historical text values that should normally be restricted.

The vulnerability arises because the endpoint's authorization logic relies on broad permissions like view_work_packages or view_project instead of enforcing granular visibility checks for journals, objects, and fields.

As a result, sensitive data such as hidden work package descriptions, restricted journal contents, project custom fields, and cancelled meeting notes can be exposed.

This vulnerability affects OpenProject versions 17.3.2 and earlier, as well as 17.4.0, and was fixed in versions 17.3.3 and 17.4.1.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive historical information stored within OpenProject.

  • Exposure of hidden work package descriptions.
  • Access to restricted journal contents.
  • Disclosure of project custom fields that may contain confidential data.
  • Revealing cancelled meeting notes that were intended to be hidden.

Such exposure can compromise project confidentiality and potentially leak sensitive organizational information to unauthorized users.

Detection Guidance

This vulnerability involves unauthorized access to the journal diff endpoint (GET /journals/:journal_id/diff/:field) in OpenProject versions 17.3.2 and earlier, and 17.4.0. Detection can focus on monitoring access to this specific endpoint, especially requests from low-privileged or unauthenticated users.

You can detect potential exploitation attempts by checking web server or application logs for unusual or unauthorized GET requests to paths matching /journals/*/diff/*.

Example commands to search logs for such requests include:

  • Using grep on Apache or Nginx logs: grep -E 'GET /journals/.*/diff/.*' /var/log/nginx/access.log
  • Using curl to test the endpoint (replace with actual journal_id and field): curl -i -X GET 'https://your-openproject-instance/journals/123/diff/field_name'

If you observe unauthorized or unexpected access to this endpoint, it may indicate attempts to exploit the vulnerability.

Mitigation Strategies

The primary mitigation is to upgrade OpenProject to version 17.3.3 or 17.4.1 or later, where the vulnerability is fixed.

Until you can upgrade, consider restricting access to the journal diff endpoint by implementing network-level controls such as firewall rules or web application firewall (WAF) rules to block unauthorized or unauthenticated requests to /journals/:journal_id/diff/:field.

Additionally, review project visibility and user permissions to minimize exposure, especially in public-project configurations.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47193. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart