dbcve.org
Supplier Relationship ManagementApplication · Sap

CVE-2025-30009

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
he Live Auction Cockpit in SAP Supplier Relationship Management (SRM) uses a deprecated java applet component within the affected SRM packages which allows an unauthenticated attacker to execute malicious script in the victim�s browser. This vulnerability has low impact on confidentiality and integrity within the scope of that victim�s browser, with no effect on 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 confidence

The Live Auction Cockpit in SAP SRM uses a deprecated Java applet component that fails to properly sanitize user input, allowing unauthenticated attackers to inject malicious scripts that execute in victims' browsers (stored XSS). This affects the confidentiality and integrity of data within the scope of the victim's browser session.

MitigationReplace or remove the deprecated Java applet component with modern, secure alternatives and implement proper input validation and output encoding. Consider migrating entirely away from Java applets given their deprecated status and known security risks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 SRM installation and version
    Check the SAP system for installed SAP SRM version using transaction code SM37 or by reviewing the SAP system information. Look for version 7.14 specifically.
    Affected if The installed SAP SRM version is exactly 7.14
  2. Verify Live Auction Cockpit is in use
    Check if the Live Auction Cockpit (transaction code: /SAPSRM/LC or similar) is accessible in the SAP SRM system. Review user authorizations and available webdynpro components.
    Affected if The Live Auction Cockpit component is accessible and actively used in the system
  3. Check for Java applet component presence
    Inspect the Live Auction Cockpit application files for the presence of deprecated Java applet components (.jar files, applet tags in JSP/HTML). Check the /SAPSRM/ directory structure for legacy applet-related code.
    Affected if Java applet files or references exist within the Live Auction Cockpit module
  4. Review input validation mechanisms
    Examine the Live Auction Cockpit code for input validation routines. Look for functions that handle user-supplied auction data, bid submissions, and cockpit parameter inputs.
    Affected if No input sanitization or validation is implemented for user inputs in the auction cockpit
  5. Verify XSS filter is absent or ineffective
    Test or inspect whether output encoding is applied before rendering user input in the browser. Check for XSS filter configurations in the SAP SRM security settings.
    Affected if User input is rendered without proper encoding, allowing script injection to persist

A user is affected if SAP SRM version 7.14 is running with the Live Auction Cockpit and its deprecated Java applet component is present and accessible without adequate input sanitization.

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

Replace or remove the deprecated Java applet component with modern, secure alternatives and implement proper input validation and output encoding. Consider migrating entirely away from Java applets given their deprecated status and known security risks.

Fix this in Supplier Relationship Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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