dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2026-24324

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
SAP BusinessObjects Business Intelligence Platform (AdminTools) allows an authenticated attacker with user privileges to execute a specific query in AdminTools that could cause the Content Management Server (CMS) to crash, rendering the CMS partially or completely unavailable and resulting in the denial of service of the Content Management Server (CMS). Successful exploitation impacts system availability, while confidentiality and integrity remain unaffected.

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

This is a denial of service vulnerability in SAP BusinessObjects BI Platform where an authenticated user with standard user privileges can execute a specific query through AdminTools that triggers a crash in the Content Management Server (CMS), making it partially or completely unavailable.

MitigationApply available SAP security patches for this vulnerability. Until patched, implement additional monitoring for abnormal AdminTools query patterns and consider restricting AdminTools access to essential administrative personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Businessobjects Business Intelligence PlatformApplication
Affected:= 430= 2025= 2027

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Identify SAP BusinessObjects BI Platform version
    Access the SAP BusinessObjects Central Management Console (CMC) or check the installation via SAP BusinessObjects Installation Manager. In CMC, go to 'About' or check the version through the 'Servers' node showing CMS version information.
    Affected if Installed version equals 430, 2025, or 2027 (or specific SPs/patches of these versions)
  2. Verify AdminTools module access for standard users
    In the CMC, navigate to 'Applications' and check the permissions assigned to standard user accounts for AdminTools. Verify which user groups have access to AdminTools functionality.
    Affected if Standard (non-admin) users have permission to access and execute queries through AdminTools
  3. Confirm Content Management Server (CMS) is running
    In the CMC, go to the 'Servers' node and locate the CMS server. Check its status indicator (green for running, red for stopped). Alternatively, attempt to log in to the CMC to verify CMS responsiveness.
    Affected if CMS is currently unresponsive, showing as stopped, or exhibits intermittent availability issues
  4. Review CMS server logs for crash events
    Access the CMS trace logs located in the SAP BusinessObjects logging directory (typically under the 'logging' or ' traces' folder in the installation directory). Search for recent timestamps and error entries indicating unexpected termination or query-related failures.
    Affected if Logs contain recent CMS crash events or fatal errors associated with AdminTools query execution

Your environment is affected if you run version 430, 2025, or 2027 of SAP BusinessObjects BI Platform, standard users have AdminTools access, and the CMS shows instability or recent crash events linked to AdminTools queries.

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 available SAP security patches for this vulnerability. Until patched, implement additional monitoring for abnormal AdminTools query patterns and consider restricting AdminTools access to essential administrative personnel only.

Fix this in Businessobjects Business Intelligence Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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