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

CVE-2025-40676

MEDIUM · 5.3 CVSS v4.0 Published 2025-10-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Insecure Direct Object Reference (IDOR) in Negotiator v3.15.2 from Biobanking and Biomolecular Resources - European Research Infrastructure (BBMRI-ERIC). This vulnerability allows an attacker to access or modify unauthorised resources by manipulating requests that use the 'userID' parameter in '/api/v3/users/<userID>', which may result in the exposure or alteration of sensitive data

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Negotiator v3.15.2 REST API. The endpoint '/api/v3/users/<userID>' accepts a userID parameter without properly validating that the authenticated user has authorization to access or modify that specific user's resources. An authenticated attacker can manipulate the userID parameter to access or alter data belonging to other users.

MitigationImplement proper object-level authorization checks to verify the requesting user has permission to access or modify the requested user resource. Use the authenticated user's own ID from the session/token rather than trusting client-supplied userID parameters.

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:L/VI:N/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. Identify Negotiator version
    Locate and inspect the Negotiator installation to determine the installed version number. Check configuration files, about pages, or version endpoints provided by the application.
    Affected if The installed version is 3.15.2 or falls within the affected range around this version.
  2. Verify REST API is enabled
    Check the Negotiator configuration to confirm the REST API module (api/v3/) is enabled and accessible.
    Affected if The REST API endpoints are accessible and operational in the environment.
  3. Confirm /api/v3/users endpoint is accessible
    Attempt to access or enumerate the /api/v3/users/<userID> endpoint. This may require checking routing configuration, URL mappings, or attempting a request if you have API access.
    Affected if The /api/v3/users/<userID> endpoint exists and accepts requests.
  4. Check authentication configuration
    Review how the API handles authentication. Verify whether a valid authenticated session or token is required to access user data endpoints.
    Affected if The endpoint accepts authenticated requests but does not properly validate that the authenticated user has permission to access the specified userID.
  5. Inspect authorization logic for user endpoints
    Examine the code or configuration that handles authorization for the /api/v3/users/<userID> endpoint. Look for object-level authorization checks that validate the requesting user's permissions against the requested userID.
    Affected if The endpoint relies on client-supplied userID without validating the authenticated user's ownership or permission to access that specific user's resources.

A user is affected if they are running Negotiator version 3.15.2 (or an affected version) with the REST API enabled, where the /api/v3/users/<userID> endpoint accepts authenticated requests without proper authorization validation of the userID parameter.

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 object-level authorization checks to verify the requesting user has permission to access or modify the requested user resource. Use the authenticated user's own ID from the session/token rather than trusting client-supplied userID parameters.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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