dbcve.org
Supplier Relationship ManagementApplication · Sap

CVE-2025-30018

HIGH · 7.5 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The Live Auction Cockpit in SAP Supplier Relationship Management (SRM) allows an unauthenticated attacker to submit an application servlet request with a crafted XML file which when parsed, enables the attacker to access sensitive files and data. This vulnerability has a high impact on the application's confidentiality, with no effect on integrity and 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 · high confidence

An unauthenticated XML External Entity (XXE) injection vulnerability in the Live Auction Cockpit of SAP Supplier Relationship Management allows attackers to submit crafted XML files via servlet requests that, when parsed, enable access to sensitive files and data on the underlying system.

MitigationApply the relevant SAP security patch for CVE-2025-30018 and disable XML external entity processing in the application's XML parser configuration to prevent file system access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Supplier Relationship ManagementApplication
Affected:= 7.14

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Supplier Relationship Management installation
    Locate the SAP SRM installation directory or check SAP system information via transaction code SM37 or SAP MII infotype commands. Look for SAP SRM component files or services running on the application server.
    Affected if SAP Supplier Relationship Management is not installed on the system.
  2. Verify SRM version is exactly 7.14
    Check the installed SAP SRM version via SAP transaction code SM51, SPAM/SAINT patch manager, or by inspecting the SRM system version file (typically in the /sapmnt/SID/sys/exe/run directory or via SAPMMC). Compare against the affected version range.
    Affected if The installed version is exactly 7.14. Versions other than 7.14 are not affected by this specific CVE.
  3. Confirm Live Auction Cockpit component is deployed
    Check if the Live Auction Cockpit module is deployed and accessible in the SAP SRM system. This can be verified via SAP transaction code SICF (activate/deactivate ICF services) by searching for Live Auction or auction-related servlet paths, or by checking the SAP SRM component deployment status.
    Affected if The Live Auction Cockpit component is not deployed or is inactive.
  4. Verify servlet endpoint accessibility
    Check if servlet endpoints for Live Auction Cockpit are exposed. In SAP, verify ICF (Internet Communication Framework) nodes under /sap/bc/rest/auction or similar paths using transaction code SICF. Attempt to access the servlet URL or review HTTP access logs.
    Affected if The servlet endpoints for Live Auction Cockpit are not exposed or accessible over HTTP/HTTPS.

The system is affected only if SAP Supplier Relationship Management version 7.14 is installed WITH the Live Auction Cockpit component deployed AND its servlet endpoints are accessible, allowing unauthenticated XML submissions to trigger the XXE 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for CVE-2025-30018 and disable XML external entity processing in the application's XML parser configuration to prevent file system access.

Recommended fix Moderate confidence

SAP Security Note patch for CVE-2025-30018 (contact SAP Support for specific note number and patch)

  1. 1. Contact SAP Support or access the SAP ONE Support Launchpad to obtain the official security patch for CVE-2025-30018.
  2. 2. Review SAP Security Note related to this XXE vulnerability in SAP SRM Live Auction Cockpit.
  3. 3. Apply the SAP Security Note patch following SAP's standard patch deployment procedures.
  4. 4. Validate the patch was applied successfully by verifying the XML parser configuration and testing the Live Auction Cockpit functionality.
  5. 5. After patching, perform security testing to confirm the XXE vulnerability is remediated.
Caveat SAP patches typically do not introduce breaking changes but should be tested in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Supplier Relationship Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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