CVE-2025-42957
Exploitation reported by one source. First attested on 2025-09-06 by GCVE · kevintel.
- Published2025-08-12
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
SAP S/4HANA allows an attacker with user privileges to exploit a vulnerability in the function module exposed via RFC. This flaw enables the injection of arbitrary ABAP code into the system, bypassing essential authorization checks. This vulnerability effectively functions as a backdoor, creating the risk of full system compromise, undermining the confidentiality, integrity and availability of the system.
Timeline
dates in UTC- 2025-08-1203:15CVE publishedNVD
- 2025-09-0616:03Listed as exploited by GCVEGCVE
- 2025-09-0616:03Exploitation first reportedGCVE
Versions per branch
Products declared by the CNA
As sap, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- SAP_SE SAP S/4HANA (Private Cloud or On-Premise)other versions: not affectedAffected
- = S4CORE 102no fix stated
- = 103no fix stated
- = 104no fix stated
- = 105no fix stated
- = 106no fix stated
- = 107no fix stated
- = 108no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-08-12
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2025-42957 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2025-09-12
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-01mrk336/CVE-2025-42957-SAP-S-4HANA-Under-Siege
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- GCVEexploitation2025-09-06
- CISA-ADPSSVC decisionpoc2025-09-12
- CNACVSS 3.19.9known since 2026-10-23
- CNAweakness (CWE)CWE-94known since 2026-10-23
- FIRST EPSSEPSS score1.7 %2026-11-08
- PoC-in-GitHubproof of concept1known since 2026-11-01
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2025-24203same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-2c3g-27ww-4q84same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Published
- 2025-08-12
- Last Modified
- 2026-06-17
- NVD status
- Deferred
- GitHub Advisory
- GHSA-2c3g-27ww-4q84
Frequently asked questions
What is CVE-2025-42957?
Is CVE-2025-42957 actively exploited?
What is the CVSS score for CVE-2025-42957?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-2c3g-27ww-4q84
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0