CVE-2025-42952
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 Business Warehouse and SAP Plug-In Basis allows an authenticated attacker to add fields to arbitrary SAP database tables and/or structures, potentially rendering the system unusable. On successful exploitation, an attacker can render the system unusable by triggering short dumps on login. This could cause a high impact on availability. Data confidentiality and integrity are not affected. No data can be read, changed or deleted.
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 confidenceSAP Business Warehouse and SAP Plug-In Basis contain a vulnerability allowing authenticated attackers to add fields to arbitrary database tables or structures through the affected component. When this manipulation occurs, the modified table structure causes short dumps (runtime errors) during login attempts, effectively rendering the system unavailable. Only availability is impacted; confidentiality and integrity remain unaffected.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP product and versionUse transaction ST03 or SM37 to confirm the installed SAP Business Warehouse or SAP Plug-In Basis version and patch levelAffected if The product is SAP Business Warehouse or SAP Plug-In Basis and the version is unpatched against this vulnerability
-
Verify authorization role for table modificationsUse transaction PFCG to review user roles for authorization objects S_DBD (Database Dictionary) or S_TABU_DIS (Table Browser) - specifically check if roles grant access to SE11 (Data Dictionary) or SE14 (Database Utility) without proper restrictionsAffected if Authenticated users have roles granting unrestricted access to table structure modifications via SE11 or SE14
-
Check SE11/SE14 access controlUse transaction SUIM to search for roles containing authorization object S_DBD with activity values 01 (Create) or 02 (Change) assigned to users beyond strictly authorized administratorsAffected if Users other than designated DBAs have modify access to Data Dictionary transaction SE11 or database utility SE14
-
Inspect recent table modification logsUse transaction SE14 to review recent modifications to database tables, or check system log (transaction SM37) for DB02 or SE14-related jobs with change operationsAffected if There are unauthorized or unexpected table structure modifications in the logs that were not initiated by the database administration team
The environment is affected if it runs unpatched SAP Business Warehouse or SAP Plug-In Basis and any authenticated user has unauthorized modify access to Data Dictionary (SE11/SE14) functions.
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 relevant SAP Security Note to address the improper authorization check when adding fields to database tables. Prior to production deployment, test that the patch does not introduce new short dumps or break existing table structures.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42952 — 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-42952 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