dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-11369

HIGH · 7.1 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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
The Comment API (GET /api/Comment and POST /api/Comment) in the affected application fails to perform authorization checks to verify that the requesting user has access to the object identified by the relatedObjectId. This Insecure Direct Object Reference (IDOR) vulnerability allows any authenticated user to read and write comments on any process across all business units by supplying an arbitrary object GUID.

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 Comment API endpoints (GET and POST /api/Comment) lack authorization validation on the relatedObjectId parameter, allowing any authenticated user to access or modify comments on any object in the system by supplying an arbitrary GUID. This IDOR vulnerability enables cross-business-unit data access to sensitive process comments.

MitigationImplement proper authorization checks to verify the requesting user has access to the object referenced by relatedObjectId before allowing comment read/write operations, enforcing object-level permission validation.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Comment API endpoints are accessible
    Send a GET request to /api/Comment with a valid authentication token but using an arbitrary relatedObjectId GUID (e.g., a random UUID). Inspect the HTTP response code and whether any comment data is returned.
    Affected if The API returns a 200 OK response with comment data for an unrelated object's GUID without returning a 403 Forbidden or authorization error.
  2. Test POST endpoint for unauthorized comment creation
    Send a POST request to /api/Comment with a valid auth token but a relatedObjectId GUID that does not belong to the authenticated user's business unit or accessible objects. Include a test comment payload.
    Affected if The API accepts the request and returns 201 Created, indicating comments can be written to objects the user should not have access to.
  3. Verify authorization behavior differs from expected
    Compare API responses when using a relatedObjectId for an object the user legitimately owns versus an object in a different business unit. Check if the responses are identical in authorization success.
    Affected if Both requests return successful comment data or allow comment creation, showing no object-level permission validation on the relatedObjectId parameter.
  4. Check API documentation or source for authorization logic
    Examine the Comment API controller code or configuration files for authorization attributes on the relatedObjectId parameter, specifically looking for ObjectLevelPermission or similar custom authorization checks.
    Affected if No explicit authorization check exists that validates the user has access to the object referenced by relatedObjectId before processing the comment request.

A user is affected if the Comment API returns or accepts comments for arbitrary relatedObjectId GUIDs without enforcing object-level access controls, allowing cross-business-unit data exposure.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks to verify the requesting user has access to the object referenced by relatedObjectId before allowing comment read/write operations, enforcing object-level permission validation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11369 — 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-11369 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