CVE-2025-42945
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 Application Server ABAP has HTML injection vulnerability. Due to this, an attacker could craft a URL with malicious script as payload and trick a victim with active user session into executing it. Upon successful exploit, this vulnerability could lead to limited access to data or its manipulation. There is no impact on availability.
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 confidenceHTML injection vulnerability in SAP NetWeaver Application Server ABAP allows attackers to embed malicious script content into URLs. When authenticated users are tricked into clicking these crafted links, the script executes within their active session context, potentially enabling limited data access or manipulation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP NetWeaver ABAP system typeExecute SAP transaction SM51 to list active application server instances, or check for ABAP stack processes via OS-level commands such as 'ps -ef | grep dw'Affected if The system is running SAP NetWeaver Application Server ABAP (AS ABAP)
-
Identify installed SAP kernel versionExecute SAP transaction SM51 and note the kernel release version, or use the SAP kernel version check utility sapkernel -v at OS levelAffected if The installed kernel version falls within the affected version range for CVE-2025-42945 (compare your version to the affected ranges once published)
-
Verify URL parameter handling is exposedCheck the SAP Internet Communication Manager (ICM) configuration via transaction SMICM or by examining the icm/filter_prefix parameters in the profileAffected if The ICM accepts and processes URL parameters without proper sanitization or the URL filtering is disabled
-
Confirm external URL access is possibleReview SAP Web Dispatcher logs or ICM trace files for requests containing script content in URL parameters, or test by submitting a benign parameter with script tagsAffected if The system allows URL parameters containing script content to be processed and reflected in responses
-
Assess user session exposureCheck if the system supports authenticated user sessions that can be exploited via malicious links, and review session management configuration in the SAP profile parameters such as login/ticket_lifetimeAffected if Authenticated users can access the system via URLs and the session context is vulnerable to script execution from crafted links
A user is affected if they run SAP NetWeaver Application Server ABAP with a vulnerable kernel version and the ICM/URL parameter handling is exposed to external requests without filtering.
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 the SAP security patch for CVE-2025-42945 when released. Until then, implement URL filtering/proxy controls to block known malicious patterns and educate users about not clicking untrusted links.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42945 — 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-42945 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