CVE-2025-42906
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 · uneditedSAP Commerce Cloud contains a path traversal vulnerability that may allow users to access web applications such as the Administration Console from addresses where the Administration Console is not explicitly deployed. This could potentially bypass configured access restrictions, resulting in a low impact on confidentiality, with no impact on the integrity or availability of the application.
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 confidenceSAP Commerce Cloud contains a path traversal vulnerability that allows users to access the Administration Console from network addresses where it is not explicitly deployed, bypassing configured access restrictions and resulting in low confidentiality impact.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Administration Console is deployedCheck the SAP Commerce Cloud installation for presence of the admin console module (typically at /admin console or /hybris/admin paths). Look for admin-related web.xml servlet mappings and Spring configuration files that define admin endpoints.Affected if The Administration Console is present and accessible on the system
-
Verify Administration Console network access controlsReview the Tomcat or SAP Commerce configuration files (such as server.xml, web.xml, or custom access control XML files) to identify which IP addresses or network ranges are explicitly allowed to access the admin console. Look for allow/deny rules or restrict attributes.Affected if Network access controls are defined but can be bypassed via path traversal, or no IP-based restrictions are configured for the admin console
-
Test for path traversal in admin console URLsAttempt to access the admin console through known path traversal patterns such as /..;/admin, /../admin console, or encoded variations like /%2e%2e/admin. Use curl or a similar tool to send requests from an unauthorized IP address.Affected if The admin console responds to path traversal requests from network addresses not in the allowed list
-
Review application-level access control configurationExamine SAP Commerce Cloud's backoffice-access.xml, local.properties, or relevant security configuration files for admin console access restrictions. Check for WebXMLAdapter or similar configuration that defines URL-to-IP mappings.Affected if Access control configurations exist but do not properly validate path-normalized requests or can be circumvented
A user is affected if the Administration Console is deployed and can be accessed via path traversal from network addresses not explicitly authorized in the access control configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataEnsure the Administration Console is only accessible from explicitly authorized network addresses by reviewing and enforcing proper access control configurations at both application and network levels.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42906 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42906 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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