dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-29997

HIGH · 8.2 CVSS v4.0 Published 2025-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
This vulnerability exists in the CAP back office application due to improper authorization checks on certain API endpoints. An authenticated remote attacker could exploit this vulnerability by manipulating API request URL to gain unauthorized access to other user accounts.

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 a broken access control vulnerability in the CAP back office application's API. The application fails to properly verify that an authenticated user is authorized to access specific resources, allowing any authenticated attacker to manipulate API request URLs to access other user accounts' data (horizontal privilege escalation). This is a classic Insecure Direct Object Reference (IDOR) or Missing Function Level Access Control issue.

MitigationImplement and enforce proper authorization checks on all API endpoints to validate that the authenticated user has permission to access the requested resource. Use indirect references and validate user-session ownership of any requested objects.

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/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 CAP back office application installation
    Search the system for CAP back office application files, services, or web applications. Check installed software lists, running processes, or web server configurations for references to 'CAP' back office or 'SAP CAP' components.
    Affected if The CAP back office application or its API component is present in the environment
  2. Locate API endpoint configurations
    Examine web server configuration files (such as nginx.conf, httpd.conf, or application-specific config), and the application's routing or endpoint definition files to identify exposed API paths.
    Affected if API endpoints are exposed and accessible over the network
  3. Verify API authentication mechanism
    Review the application's authentication configuration, session management settings, and API middleware to confirm that user authentication is required for API access.
    Affected if The API accepts authenticated requests but lacks proper authorization validation on resource access
  4. Test for direct object reference vulnerabilities
    Log in to the API with a standard user account, then attempt to access resources belonging to other users by manipulating object identifiers (IDs, UUIDs) in API request URLs or request bodies. Compare the response with the expected access boundaries.
    Affected if An authenticated user can access or modify data belonging to another user by changing identifiers in API requests
  5. Inspect API access control policies
    Review the application's authorization configuration, middleware, or access control lists to determine if function-level access control checks exist on API endpoints.
    Affected if API endpoints lack enforcement of user-session ownership validation for requested resources

If the CAP back office application API is exposed and allows authenticated users to access other users' data by manipulating request parameters, the environment is affected by this vulnerability.

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 and enforce proper authorization checks on all API endpoints to validate that the authenticated user has permission to access the requested resource. Use indirect references and validate user-session ownership of any requested objects.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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