dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-42983

HIGH · 8.5 CVSS v3.1 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 Business Warehouse and SAP Plug-In Basis allows an authenticated attacker to drop arbitrary SAP database tables, potentially resulting in a loss of data or rendering the system unusable. On successful exploitation, an attacker can completely delete database entries but is not able to read any data.

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

SAP Business Warehouse and SAP Plug-In Basis contain a vulnerability allowing authenticated attackers to drop arbitrary SAP database tables via improper authorization checks, leading to potential data loss or complete system unavailability. The attacker has delete privileges but cannot read the data.

MitigationRestrict database-level privileges for affected SAP user roles, implement principle of least privilege for table drop operations, and apply SAP security patches when available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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
    Run transaction code 'SM37' or use SAP MII version checker to determine if the system is running SAP Business Warehouse (BW) or SAP Plug-In Basis. Check SAP note 3593241 for version-specific details.
    Affected if System is running SAP Business Warehouse or SAP Plug-In Basis and the installed version is within the affected range per SAP security notes.
  2. Verify SAP Kernel version
    Execute transaction code 'SKRN' or use SAPMMC to display the kernel version. Compare against the patched kernel version indicated in the relevant SAP security note for this CVE.
    Affected if Kernel version is older than the patched version specified in SAP security patches for CVE-2025-42983.
  3. Check database privilege assignments
    Use transaction code 'SUIM' or 'PFCG' to review role definitions. Inspect database-level privileges assigned to users, specifically checking for DROP TABLE or equivalent destructive database operation permissions.
    Affected if Users possess database-level DROP or DELETE privileges that exceed their intended application role permissions.
  4. Review BW-specific authorizations
    Execute transaction code 'RSEC' or check SAP BW authorizations via 'RSUA' to examine whether Business Warehouse service accounts or technical users have elevated database operation rights.
    Affected if BW service accounts or technical users have been granted unrestricted database object manipulation rights beyond standard BW processing needs.
  5. Audit recent database operations logs
    Review SAP system logs via transaction code 'SM37' or database audit trails for any DROP TABLE commands executed without corresponding application-level justification.
    Affected if DROP TABLE or equivalent destructive database operations were executed by authenticated users lacking explicit application-tier authorization for those actions.

A system is affected if it runs a vulnerable SAP Business Warehouse or SAP Plug-In Basis version AND has users or service accounts with excessive database-level drop privileges beyond their assigned application roles.

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

Restrict database-level privileges for affected SAP user roles, implement principle of least privilege for table drop operations, and apply SAP security patches when available.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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