dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-42910

CRITICAL · 9.0 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
Due to missing verification of file type or content, SAP Supplier Relationship Management allows an authenticated attacker to upload arbitrary files. These files could include executables which might be downloaded and executed by the user which could host malware. On successful exploitation an attacker could cause high impact on confidentiality, 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 · moderate confidence

SAP Supplier Relationship Management lacks proper file type and content validation on file uploads, allowing authenticated attackers to upload arbitrary files including executables. These malicious files can be subsequently downloaded and executed by other users, potentially leading to malware propagation and full system compromise.

MitigationImplement strict file type validation using both extension allowlisting and content-based verification (magic bytes/file signatures). Store uploaded files outside web root with randomized filenames, and serve them with proper Content-Disposition headers to prevent execution.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

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 landscape using transaction SE16N or SM37 to list installed SAP SRM components, or query the SAP system version information via SAP MII version checker or SAP LMDB.
    Affected if SAP Supplier Relationship Management is installed and the version falls within the affected range (verify against SAP security notes for CVE-2025-42910).
  2. Locate file upload functionality in SRM
    Navigate to SAP SRM portal components: supplier portal, bidding workspace, or purchase requisition modules that accept file attachments. Identify upload endpoints in transaction SE80 or via web server logs.
    Affected if File upload capability exists in the SRM environment and is accessible to authenticated users.
  3. Inspect upload validation configuration
    Review SAP SRM upload handler configuration in transaction SM30 for table V_UPLOAD or check web.xml/UploadServlet configurations in SAP NetWeaver for file type restrictions.
    Affected if No extension allowlisting or content-based validation (magic bytes/file signatures) is configured for uploaded files.
  4. Verify uploaded file storage location
    Check the file system path where uploaded files are stored via SAP transaction AL11 or review the upload handler configuration for the storage directory path.
    Affected if Uploaded files are stored within the web root or a publicly accessible directory rather than outside the web root.
  5. Test file upload for executable types
    Attempt to upload a test file with executable extension (.exe, .bat, .sh, .asp, .jsp) via the SRM file upload interface and verify if the upload succeeds without rejection.
    Affected if The system accepts and stores executable file types without rejecting them based on file extension or content type.

An environment is affected if SAP SRM is running with file upload functionality enabled and without proper file type/content validation allowing executable files to be uploaded and stored in accessible locations.

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

Implement strict file type validation using both extension allowlisting and content-based verification (magic bytes/file signatures). Store uploaded files outside web root with randomized filenames, and serve them with proper Content-Disposition headers to prevent execution.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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