dbcve.org
Supplier Relationship ManagementApplication · Sap

CVE-2025-30010

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
The 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 craft a malicious link, which when clicked by a victim, redirects the browser to a malicious site. On successful exploitation, the attacker could cause low impact on confidentiality and integrity with no impact on the 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

The Live Auction Cockpit in SAP Supplier Relationship Management (SRM) contains a deprecated Java applet component. An unauthenticated attacker can craft a malicious link that, when clicked by a victim, redirects the browser to an attacker-controlled malicious site. This open redirect vulnerability stems from the use of obsolete Java applet technology that lacks modern security controls.

MitigationRemove or disable the deprecated Java applet component from the Live Auction Cockpit and replace it with modern, secure web technologies. Implement URL validation and filtering to prevent malicious redirects, and consider implementing click-through warning pages for external links.

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 information: log into SAP SM37 or use transaction code 'SM51' to view installed SAP components and their version numbers. Look specifically for 'SAP Supplier Relationship Management' and confirm the version is 7.14.
    Affected if SAP SRM version 7.14 is installed and running.
  2. Locate the Live Auction Cockpit component
    Access the SAP SRM administration console or transaction code related to SRM. Navigate to the Live Auction functionality. Verify if the Live Auction Cockpit module is present and enabled in the system.
    Affected if The Live Auction Cockpit module is present and accessible in the SRM system.
  3. Check for deprecated Java applet files
    Inspect the web application files for the Live Auction Cockpit. Look for Java applet-related files (.jar, .class files) in the SRM web directory, typically found under the Live Auction Cockpit application path. Search for <applet> or 'java plugin' references in the Cockpit's HTML or JSP pages.
    Affected if Java applet components (.jar files, .class files) or applet tag references exist within the Live Auction Cockpit web files.
  4. Verify URL redirect handling
    Examine the Live Auction Cockpit configuration and source code for URL redirect or forwarding logic. Look for parameters that control redirection (such as 'redirect', 'url', 'target', or similar). Test if the application accepts arbitrary URLs as redirect targets without validation.
    Affected if The Live Auction Cockpit accepts and follows external URLs in redirect parameters without validation or warning pages.

If SAP SRM version 7.14 is running with the Live Auction Cockpit enabled, and the deprecated Java applet component is present and processes unvalidated redirect URLs, the environment is affected by this open redirect 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

Remove or disable the deprecated Java applet component from the Live Auction Cockpit and replace it with modern, secure web technologies. Implement URL validation and filtering to prevent malicious redirects, and consider implementing click-through warning pages for external links.

Fix this in Supplier Relationship Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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