dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-42891

MEDIUM · 5.5 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 missing authorization check in SAP Enterprise Search for ABAP, an attacker with high privileges may read and export the contents of database tables into an ABAP report. This could lead to a high impact on data confidentiality and a low impact on data integrity. There is no impact on application's availability.

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

A missing authorization check in SAP Enterprise Search for ABAP allows authenticated users with high privileges to bypass access controls and read/export the contents of arbitrary database tables into an ABAP report, resulting in unauthorized data disclosure.

MitigationApply the relevant SAP security patch for this authorization vulnerability and review Enterprise Search authorization roles to ensure proper table access restrictions are enforced.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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. Verify SAP Enterprise Search for ABAP is installed
    Log into SAP ABAP system and navigate to SAP Menu > Enterprise Search or use transaction code /n/SAP/RSA-EA-SEARCH. Alternatively, check transaction SE11 for table /SSA/ES_DYNAMIC_CONFIG or check system landscape via transaction SLM0.
    Affected if Enterprise Search is installed and active in the ABAP system
  2. Confirm the ABAP kernel and support package level
    Execute transaction SAINT or look at system information via transaction SM37 and check the SAP kernel version (transaction SM51 shows kernel release). Compare against any applicable SAP Security Notes for this vulnerability.
    Affected if The SAP kernel or support package level has not received the relevant security patch for CVE-2025-42891
  3. Review Enterprise Search authorization roles
    Use transaction PFCG to examine roles assigned to Enterprise Search, such as /SSA/ES_* roles. Check if role /SSA/ES_AUTHORIZATION or similar authorization role objects (like S_TABU_DIS, S_TABU_NAM) are properly configured with restricted table access.
    Affected if Authorization roles grant unrestricted table access or lack proper table access restrictions (S_TABU_DIS with unrestricted activity field)
  4. Inspect user privilege assignments
    Use transaction SUIM or SU01 to review users assigned Enterprise Search roles. Check if users with high privileges (such as SAP_ALL or custom roles) have the ability to execute ABAP reports that can read arbitrary database tables.
    Affected if Users have roles granting broad table read access without proper row-level or table-specific restrictions
  5. Audit recent Enterprise Search table access
    Review transaction STATS or use transaction SE11 to check table /SSA/ES_QUERY_LOG if available. Alternatively, monitor transaction SE38 for execution of reports that access tables directly (such as SE16N with debug mode).
    Affected if There are records of unauthorized table access or execution of reports that bypass standard table authorization checks

User is affected if SAP Enterprise Search for ABAP is enabled and the system lacks the security patch or proper authorization role restrictions that prevent users from reading arbitrary database tables.

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 patch for this authorization vulnerability and review Enterprise Search authorization roles to ensure proper table access restrictions are enforced.

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-42891 — 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-42891 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