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

CVE-2025-61876

MEDIUM · 5.0 CVSS v3.1 Published 2025-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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 /tenants/{id} API endpoint in Inforcer Platform version 2.0.153 allows an authenticated user with low privileges to enumerate and access tenant information belonging to other clients via modification of the tenant ID in the request URL.

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

Insecure Direct Object Reference (IDOR) vulnerability in the /tenants/{id} API endpoint of Inforcer Platform v2.0.153 allows authenticated low-privilege users to access tenant data belonging to other clients by manipulating the tenant ID parameter in the request URL. The application fails to validate that the requesting user has authorization to access the specific tenant resource before returning sensitive tenant information.

MitigationImplement proper authorization checks to verify the authenticated user has permissions to access the requested tenant resource before returning any data. Enforce tenant isolation at the application layer and validate user-client associations on all tenant-scoped API requests.

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
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm Inforcer Platform installation and version
    Locate the Inforcer Platform application and identify its installed version (v2.0.153). Check installation directories, software inventory, or application about/settings pages for version information.
    Affected if The installed version matches v2.0.153 exactly.
  2. Verify /tenants/{id} API endpoint is exposed
    Identify if the application exposes a REST API with the /tenants/{id} endpoint. Check API documentation, network traffic, or attempt a request to this endpoint structure.
    Affected if The /tenants/{id} endpoint is accessible and responds to requests.
  3. Confirm user authentication is enabled
    Determine if the application supports user authentication, even for low-privilege accounts. Verify that the API requires authentication tokens or session credentials.
    Affected if The application allows authenticated users (including low-privilege accounts) to make API requests.
  4. Test tenant isolation on API requests
    Using an authenticated low-privilege user account assigned to one tenant, attempt to access /tenants/{id} with a different tenant's ID. Compare the response against expected authorization behavior.
    Affected if The API returns tenant data for a tenant ID that the authenticated user is NOT authorized to access.
  5. Review authorization validation for tenant resources
    Inspect application logs, code, or configuration to determine if the /tenants/{id} endpoint validates that the requesting user has permission to access the specified tenant before returning data.
    Affected if The application does not validate user-tenant association or authorization before returning tenant data.

A user is affected if they run Inforcer Platform v2.0.153 and the /tenants/{id} endpoint returns data for tenant IDs outside the authenticated user's authorized scope.

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 authenticated user has permissions to access the requested tenant resource before returning any data. Enforce tenant isolation at the application layer and validate user-client associations on all tenant-scoped API requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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