dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-42967

CRITICAL · 9.9 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 →
100/100
Remediation priority · Urgent
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
SAP S/4HANA and SAP SCM Characteristic Propagation has remote code execution vulnerability. This allows an attacker with user level privileges to create a new report with his own code potentially gaining full control of the affected SAP system causing high impact on confidentiality, integrity, and availability of the application.

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 remote code execution vulnerability in the Characteristic Propagation component of SAP S/4HANA and SAP SCM allows authenticated users with standard user-level privileges to create custom reports containing malicious code, achieving arbitrary code execution and full system compromise.

MitigationApply the relevant SAP Security Note patch for CVE-2025-42967 immediately; until then, restrict report creation permissions and monitor for unauthorized report modifications in the Characteristic Propagation module.

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 checks

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

  1. Identify SAP product and version
    Execute transaction code /n/IHB/VERSION in SAP S/4HANA or SAP SCM system to retrieve the SAP system version, or use transaction SM37 to check system details. Compare the installed version against SAP S/4HANA and SAP SCM version ranges relevant to CVE-2025-42967.
    Affected if The installed SAP S/4HANA or SAP SCM version falls within the affected version range for this CVE.
  2. Verify Characteristic Propagation component status
    Execute transaction code /n/CPD/ADMIN or search for Characteristic Propagation module in SAP transaction SE11 by querying table TADIR for objects related to characteristic propagation. Check if the component is installed and active in the system.
    Affected if The Characteristic Propagation component is installed and active in the SAP system.
  3. Review custom reports in Characteristic Propagation
    Execute transaction code /n/SA38 or SE38 and search for reports in the Characteristic Propagation namespace (typically under package or namespace containing 'CPD' or 'Characteristic Propagation'). Inspect report directory tables like TRDIR or TADIR for custom-developed reports in this module.
    Affected if Custom or unauthorized reports exist in the Characteristic Propagation component.
  4. Audit user authorizations for report creation
    Execute transaction code /n/PFCG to review roles assigned to standard users. Check authorization object S_PROGRAM for program execution permissions related to Characteristic Propagation reports. Use transaction SUIM to query for users with report creationauthorizations in this module.
    Affected if Standard user accounts possess authorization to create or modify reports within the Characteristic Propagation component.
  5. Inspect system logs for suspicious report activity
    Execute transaction code /n/BC_GP_LOG or review system logs via transaction SM37 for recent activity involving Characteristic Propagation reports. Check transaction SLG1 for application logs related to report generation in this component.
    Affected if Recent logs show creation or execution of reports in Characteristic Propagation that were not initiated by authorized administrators.

The environment is affected if SAP S/4HANA or SAP SCM is running a vulnerable version, the Characteristic Propagation component is active, and standard users have report creation permissions or unauthorized custom reports exist in the Characteristic Propagation module.

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

Apply the relevant SAP Security Note patch for CVE-2025-42967 immediately; until then, restrict report creation permissions and monitor for unauthorized report modifications in the Characteristic Propagation module.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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