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

CVE-2026-54105

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 U.S. Government Accountability Office (GAO) Electronic Protest Docketing System (EPDS) and Civilian Board of Contract Appeals (CBCA) Electronic Docketing System (EDS) expose sensitive account information through the 'update-profile/' API endpoint. A remote, unauthenticated attacker can submit a request containing an arbitrary 'user_id' parameter and receive a JSON response containing account-specific information, including the associated email address.

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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability combined with information disclosure. The 'update-profile/' API endpoint in GAO's EPDS and CBCA's EDS systems fails to validate user authentication and authorization, allowing any unauthenticated attacker to submit an arbitrary 'user_id' parameter and receive a JSON response containing sensitive account information including email addresses.

MitigationImplement proper authentication and authorization checks on the 'update-profile/' endpoint to ensure only authenticated users can access their own profile data, and validate that the requested user_id matches the authenticated user's identity.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if the update-profile endpoint is exposed
    Review API documentation or web server configuration files to locate routes for 'update-profile/' in GAO EPDS or CBCA EDS systems
    Affected if The endpoint is publicly accessible without authentication requirements
  2. Verify authentication is required for profile access
    Send an HTTP GET or POST request to the update-profile/ endpoint without providing any authentication credentials (no session token, cookie, or Authorization header)
    Affected if The server accepts the request and returns a response instead of rejecting it with a 401/403 error
  3. Test for IDOR via user_id parameter manipulation
    Send a request to update-profile/ with an arbitrary user_id value (e.g., user_id=1 or user_id=999) as a query parameter or in the request body, without authenticating
    Affected if The server processes the request and returns profile data for the specified user_id without validating ownership
  4. Confirm sensitive information disclosure
    Examine the API response for the presence of sensitive fields such as email addresses, personal details, or other account information
    Affected if The response contains email addresses or other sensitive data belonging to the user specified in the user_id parameter
  5. Compare installed version to affected range
    Check the installed version of GAO EPDS or CBCA EDS against any vendor release notes or version documentation referencing CVE-2026-54105
    Affected if The installed version falls within the range of versions containing the vulnerable endpoint without the fix applied

A user is affected if the update-profile/ endpoint accepts unauthenticated requests and returns sensitive account information (including email addresses) when arbitrary user_id values are submitted.

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 authentication and authorization checks on the 'update-profile/' endpoint to ensure only authenticated users can access their own profile data, and validate that the requested user_id matches the authenticated user's identity.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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