Summary
OpenProject's journal diff endpoint exposes hidden historical field values without properly enforcing object and field-level visibility controls.
When attackers can query this endpoint, they may retrieve sensitive information from past states of records that should remain hidden, creating a privacy and data disclosure risk.
Affected context
This vulnerability appears in OpenProject's web-based project management environment where journal history and change diffs are exposed via an API or web endpoint.
It becomes relevant when access controls and visibility rules on objects and specific fields are expected to hide certain values but the journal diff endpoint still returns them.
Deployments that rely heavily on role-based visibility, confidential projects, or restricted fields are particularly at risk when historical data is accessible through the diff interface.
Exploit preconditions
- Attack surface: The journal diff endpoint exposed over HTTP(S) as part of the OpenProject application.
- Required access: Ability to invoke the endpoint, typically via a valid user session or API access; elevated roles are not strictly required if visibility checks are missing.
- Trigger point: Requesting diffs for journal entries associated with objects or fields that have restricted visibility or are hidden from the current user.
- Why exploitation is possible: The endpoint computes and returns historical field values without enforcing the same object-level and field-level authorization and visibility rules applied elsewhere in the application.
Why this happens
The underlying issue is a mismatch between data visibility expectations and the authorization logic implemented in the journal diff endpoint.
While OpenProject enforces visibility on objects and certain fields in normal views, the diff computation code bypasses or incompletely applies these checks when assembling historical changes.
This aligns with CWE-200 (Exposure of Sensitive Information) and CWE-862 (Missing Authorization): sensitive data from historical records is returned to callers without verifying that they are authorized to see those objects or fields.
Potential impact
- Unauthorized users may access hidden historical field values, including potentially sensitive project or user data.
- Confidential project details or internal notes could be revealed through change history.
- Data protection and privacy commitments may be undermined, impacting regulatory compliance.
- Information leakage can facilitate further attacks such as social engineering or privilege escalation attempts.
General mitigation guidance
Mitigation generally focuses on aligning history and diff endpoints with the same authorization and visibility model used in primary object views.
Common defensive patterns include:
- Enforcing object-level authorization checks before returning any journal or diff data.
- Applying field-level visibility rules to historical values so hidden fields remain hidden in all contexts.
- Centralizing access control logic to avoid duplicated or inconsistent checks across endpoints.
- Designing APIs so that historical data is treated as sensitive by default and only exposed when explicitly required and authorized.
How teams detect issues like this
High-level detection often includes:
- Code review to ensure all endpoints that expose history, audit logs, or diffs consistently invoke shared authorization and visibility checks.
- Static analysis rules searching for direct access to journal or history models without accompanying permission checks.
- Security testing focusing on role-based access control, including attempts to retrieve hidden or restricted fields via history and diff functions.
- Policy-driven inspections that flag endpoints returning raw database values or historical data without context-aware filtering.

