CVE-2025-25243
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 Supplier Relationship Management (Master Data Management Catalog) allows an unauthenticated attacker to use a publicly available servlet to download an arbitrary file over the network without any user interaction. This can reveal highly sensitive information with no impact to integrity or availability.
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 confidenceSAP Supplier Relationship Management (SRM) Master Data Management Catalog contains a path traversal vulnerability in a publicly accessible servlet that allows unauthenticated remote attackers to download arbitrary files from the server filesystem. No authentication or user interaction is required, enabling complete confidentiality compromise of any file the SAP process has read access to.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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 SAP SRM MDM Catalog is installedCheck your SAP system for installation of Supplier Relationship Management (SRM) with Master Data Management (MDM) Catalog component. Use SAP transaction SE16 or check SAP Solution Manager for installed software components.Affected if SAP SRM with MDM Catalog component is present in the environment
-
Verify network exposure of the vulnerable servletDetermine if the SAP SRM web services are exposed to untrusted networks. Check SAP Gateway configuration and web dispatcher settings for public-facing endpoints related to SRM.Affected if The SRM MDM Catalog servlet is accessible from untrusted networks without authentication
-
Confirm servlet availability without authenticationLocate the publicly accessible servlet endpoint for SAP SRM MDM Catalog. This is typically exposed through SAP Internet Communication Framework (ICF) or web services. Use SAP transaction SICF to review exposed services.Affected if The servlet can be accessed without providing SAP credentials
-
Test for path traversal vulnerabilityAttempt to access files outside the intended directory by manipulating URL paths with traversal sequences (such as ../../) to the exposed servlet endpoint.Affected if The servlet allows traversal sequences and returns files from the server filesystem without authentication
-
Review access permissions on sensitive filesIdentify what files the SAP process user has read access to on the operating system. Check SAP OS-level user permissions and directory access rights.Affected if The SAP process user has broad filesystem read permissions, enabling exposure of sensitive configuration or data files
A user is affected if SAP SRM with MDM Catalog is installed and the vulnerable servlet is network-accessible without authentication, allowing unauthenticated path traversal file downloads.
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 dataApply the relevant SAP Security Note to patch the vulnerable servlet, or restrict access to the affected servlet through network-level filtering or SAP Gateway configuration if a patch is not immediately available.
- 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-25243 — 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-25243 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