dbcve.org
Open RedirectWeakness · CWE-601

CVE-2025-42981

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 an open redirect vulnerability in SAP NetWeaver Application Server ABAP, an unauthenticated attacker could craft a URL link embedding a malicious script at a location not properly sanitized. When a victim clicks on this link, the script executes within the victim's browser, redirecting them to a site controlled by the attacker. This allows the attacker to access and/or modify restricted information related to the web client. While the vulnerability poses no impact on data availability, it presents a considerable risk to confidentiality and integrity.

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 confidence

Open redirect vulnerability in SAP NetWeaver Application Server ABAP allows unauthenticated attackers to embed malicious scripts in crafted URLs. When victims click these links, the script executes in their browser and redirects them to attacker-controlled sites, enabling access or modification of restricted web client information.

MitigationImplement proper URL validation and sanitization on redirect parameters to prevent external site redirection; validate all redirect destinations against an allowlist of permitted domains.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAP NetWeaver AS ABAP installation
    Check for SAP NetWeaver processes or review system inventory for 'SAP NetWeaver Application Server ABAP' or 'AS ABAP' entries
    Affected if SAP NetWeaver AS ABAP is not present on the system, the vulnerability does not apply
  2. Identify installed ABAP version
    Execute transaction code SM51 to view the release version, or use the SAP MII version checker, or inspect the kernel version via 'disp+work -v' command
    Affected if The installed version falls within the affected range for this CVE; if version is unknown, assume potential exposure
  3. Verify web client access is enabled
    Check SAP ICM (Internet Communication Manager) configuration via transaction SMICM or review icm/accept_all_unsafe_html parameter in profile
    Affected if ICM/web client is enabled and accessible externally; open redirect requires HTTP/HTTPS exposure through ICM
  4. Test for vulnerable redirect parameters
    Attempt a crafted URL with a redirect parameter pointing to an external domain (for example, a URL parameter like 'redirect=' or 'url=' with '://external-site.com'), and observe if the application permits the redirect without validation
    Affected if The application accepts and follows redirects to arbitrary external domains without validating against an allowlist
  5. Inspect URL validation configuration
    Review SAP Logon Ticket configuration and custom ICF (Internet Communication Framework) handler settings via transaction SICF for any custom redirect handlers
    Affected if No custom URL validation or allowlist filtering is implemented on redirect parameters in the ICF layer

The environment is affected if SAP NetWeaver AS ABAP is running with web client/ICM exposed and lacks proper URL allowlist validation on redirect parameters.

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 proper URL validation and sanitization on redirect parameters to prevent external site redirection; validate all redirect destinations against an allowlist of permitted domains.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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 locally
dbcve dependency scanner

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