dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-42908

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 a Cross-Site Request Forgery (CSRF) vulnerability in SAP NetWeaver Application Server for ABAP, an authenticated attacker could initiate transactions directly via the session manager, bypassing the first transaction screen and the associated authorization check. This vulnerability could allow the attacker to perform actions and execute transactions that would normally require specific permissions, compromising the integrity and confidentiality of the system by enabling unauthorized access to restricted functionality. There is no impact to availability from this vulnerability.

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 confidence

A CSRF vulnerability in SAP NetWeaver Application Server for ABAP allows authenticated attackers to bypass the first transaction screen authorization check by directly initiating transactions through the session manager. This enables unauthorized execution of privileged transactions and access to restricted functionality by tricking authenticated users into submitting malicious requests.

MitigationImplement anti-CSRF tokens for transaction requests, validate request origins/referers, and enable SAP's built-in CSRF protection mechanisms in the session manager to ensure all transaction calls go through proper authorization validation.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify SAP NetWeaver ABAP version
    Execute transaction code 'SM51' or use ABAP report 'SAPREORG' to display the SAP kernel version and ABAP application server release. Alternatively, check transaction 'SPAM' or 'SUM' for system version information.
    Affected if The installed version falls within the affected range for CVE-2025-42908 but has not been patched.
  2. Verify CSRF protection status in session manager
    Access transaction 'SICF' (ICF Services) and check the security settings for '/sap/bc/rest/...' service handlers. Look for CSRF token validation configuration in the session management settings accessed via transaction 'SCSMR' or check profile parameter 'login/accept_sso2_ticket' and related CSRF settings in 'SMT1'.
    Affected if CSRF token validation is disabled or not enforced for transaction requests.
  3. Check referer/origin validation configuration
    Use transaction 'SICF' and inspect the ICF paths '/sap/public/...' and '/sap/bc/...' for referer header validation settings. Check profile parameters 'icm/accept_all_trusted_clients' and verify if 'Validate HTTP Referer' is enabled in the ICM settings via transaction 'ICM monitor' (transaction 'ICM').
    Affected if Referer validation is disabled or set to permissive values allowing cross-origin requests.
  4. Inspect transaction execution security settings
    Use transaction 'SE93' to review transaction code parameter configurations. Check if transactions have 'SKIP AUTH CHECK' or similar bypass parameters enabled. Use transaction 'AUTH' to review authorization object 'S_TCODE' for any overly permissive role assignments.
    Affected if Transactions can be initiated without proper authorization checks through direct URL invocation.
  5. Review trusted RFC and dialog user configurations
    Execute transaction 'SMC0' or 'SMT1' to review trusted relationship settings. Check transaction 'SU01' for dialog users with broad transaction access that could be exploited via CSRF. Use transaction 'RSUSR002' to identify users with excessive transaction code authorizations.
    Affected if Trusted RFC configurations allow cross-system CSRF exploitation or users have unnecessary privileged transaction access.

A system is affected if it is an unpatched SAP NetWeaver ABAP instance where CSRF token validation is disabled, referer validation is permissive, or transaction requests can bypass the first screen authorization check.

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 anti-CSRF tokens for transaction requests, validate request origins/referers, and enable SAP's built-in CSRF protection mechanisms in the session manager to ensure all transaction calls go through proper authorization validation.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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