CVE-2025-42922
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 · uneditedSAP NetWeaver AS Java allows an attacker authenticated as a non-administrative user to use a flaw in an available service to upload an arbitrary file. This file when executed can lead to a full compromise of confidentiality, integrity and availability of the system.
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 confidenceSAP NetWeaver AS Java contains a file upload vulnerability in an available service that allows authenticated non-administrative users to upload arbitrary files. When these uploaded files are executed, they enable full compromise of system confidentiality, integrity, and availability.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP NetWeaver AS Java is installedCheck for the presence of SAP NetWeaver AS Java by examining running Java processes, the SAP system landscape, or by querying the SAP MMC/SAP Control. Look for SAP J2EE Engine processes in system process lists.Affected if The system is running SAP NetWeaver AS Java
-
Identify the NetWeaver AS Java versionUse SAP LM J2EE or query the SAP System Information via SAPMMC -> System -> Jump to SM37, or execute the SAP command 'jstart -version' from the SAP instance directory. Alternatively, check the SAR file or patch level in the system.Affected if The installed version has not yet received the security patch for CVE-2025-42922
-
Locate enabled file upload servicesAccess SAP SM37 (CCMS Monitoring) or use transaction code SICF in the SAP GUI to examine active ICF services. Look for services related to file upload, webdynpro, or web services that handle file transfers. Check the icman.log or default trace files for entries mentioning file upload handlers.Affected if A file upload service is exposed and active in the ICF tree without proper access restrictions
-
Review non-administrative user permissions for upload capabilitiesUse SAP transaction SUIM to query users with roles containing upload permissions, or check transaction PFCG for roles assigned to standard (non-SAP_ALL) users. Examine the S_DATASET authorization object for file write access, and look for UPLOAD authorizations in affected services.Affected if Non-administrative users have authorizations to upload files to the system (S_DATASET with WRITE, or specific upload-related roles)
-
Inspect upload directories for unexpected filesExamine standard SAP upload directories such as /usr/sap/*/DVEBMGS*/data, /tmp, or custom upload paths defined in the application. Check transaction AL11 for configured directory structures. Review file system timestamps and ownership of recently created files.Affected if Unexpected or unauthorized files exist in known upload directories, especially executable or JSP files
If the environment runs SAP NetWeaver AS Java, has a file upload service enabled in ICF, and allows authenticated non-administrative users to upload files, the system is affected by CVE-2025-42922.
Generated from the published advisory. Verify against your own configuration.
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 dataApply SAP security patches for CVE-2025-42922 immediately and review file upload permissions for non-administrative users until the patch is deployed.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-42922 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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