# CVE-2025-31324: SAP NetWeaver Unrestricted File Upload

> Unauthenticated attackers can upload malicious binaries to SAP NetWeaver Visual Composer due to missing authorization checks, leading to potential system compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 29 Apr 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-7w9p-pr7x-mjw2

## What is CVE-2025-31324?

CVE-2025-31324 is a critical missing authorization vulnerability in Sap Netweaver, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP NetWeaver Visual Composer Metadata Uploader is not protected with a proper authorization, allowing unauthenticated agent to upload potentially malicious executable binaries that could severely harm the host system. This could significantly affect the confidentiality, integrity, and availability of the targeted system.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-31324?

It affects 1 product.


Products: Sap Netweaver.

## How do I fix CVE-2025-31324?

No fix has been published for CVE-2025-31324 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 20 May 2025.

## Is CVE-2025-31324 being exploited?

Yes. Attackers have exploited CVE-2025-31324 in the wild since at least 29 Apr 2025, including in ransomware campaigns.

Public exploit code:

- CVE-2025-31324, SAP Exploit (github_poc): https://github.com/redrays-io/CVE-2025-31324
- sap netweaver 0day poc by shinyhunters (scattered lapsus$ hunters) affecting all 7.x CVE-2025-31324 (github_poc): https://github.com/antichainalysis/sap-netweaver-0day-CVE-2025-31324
- https://github.com/Onapsis/Onapsis_CVE-2025-31324_Scanner_Tools (github_poc): https://github.com/Onapsis/Onapsis_CVE-2025-31324_Scanner_Tools
- CVE-2025-31324 & CVE-2025-42999 vulnerability and compromise assessment tool (github_poc): https://github.com/Onapsis/Onapsis-Mandiant-CVE-2025-31324-Vuln-Compromise-Assessment
- https://github.com/NULLTRACE0X/CVE-2025-31324 (github_poc): https://github.com/NULLTRACE0X/CVE-2025-31324
- Proof-of-Concept for CVE-2025-31324: Unauthenticated upload in SAP NetWeaver Visual Composer Metadata Uploader (github_poc): https://github.com/ODST-Forge/CVE-2025-31324_PoC

## Other vulnerabilities in Sap Netweaver

- [CVE-2021-38163](https://insights.sbomify.com/CVE-2021-38163/): SAP NetWeaver Unrestricted File Upload (critical 9.9, exploited in the wild)
- [CVE-2025-42999](https://insights.sbomify.com/CVE-2025-42999/): SAP NetWeaver Deserialization (critical 9.1, exploited in the wild)
- [CVE-2013-6822](https://insights.sbomify.com/CVE-2013-6822/): XML external entity in n/a (critical 10.0)
- [CVE-2011-1517](https://insights.sbomify.com/CVE-2011-1517/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-1592](https://insights.sbomify.com/CVE-2013-1592/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31324 and fix it if it is affected.

What it is: CVE-2025-31324 is a critical missing authorization vulnerability in Sap Netweaver, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-31324 in the wild since at least 29 Apr 2025, including in ransomware campaigns.

Affected product: Sap Netweaver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31324/ (Markdown: https://insights.sbomify.com/CVE-2025-31324/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31324
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31324
- OSV: https://osv.dev/vulnerability/CVE-2025-31324

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31324/
Summaries are generated and may contain mistakes; the official description above is the record.