Skip to content

Cross-Product Authorization Gap in V3 Locations Allows an Authenticated User to Modify Other Products' Endpoint Records

Moderate
svader0 published GHSA-p3vg-56r7-3qf8 Sep 4, 2026

Software

DefectDojo (Open Source)

Affected versions

>= 3.0.0, <= 3.2.201

Patched versions

3.2.300
DefectDojo (Pro)
>= 3.0.0, <= 3.2.201
3.2.300

Description

Impact

When the V3 Locations feature is enabled, which is the default, an authenticated user with membership on a single product could obtain standing over endpoint records belonging to other products, and then modify or remove records that those other products rely on. No administrator access was required.

Reading the shared labels on such a record is a separate issue, tracked in GHSA-rr5c-4hrj-f5wp.

Patches

Resolved by scoping endpoint modification and removal to the requesting product's own references, and by authorizing the object named in each request rather than only the record it hangs from. Upgrade to 3.2.300 (Open Source and Pro).

Workarounds

No complete workaround; upgrade to 3.2.300.

References

The Pro fix ships in Pro 3.2.300.

We thank riodrwn for the responsible disclosure and assistance.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVE ID

No known CVE

Weaknesses

Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Learn more on MITRE.

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.