dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-0502

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-12
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 No privileges

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 insufficient CSRF protection in SAP BusinessObjects Business Intelligence Platform ,an authenticated user could be tricked by an attacker to send unintended requests to the web server. This has low impact on integrity and availability of the application. There is no impact on confidentiality of the 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

This is a Cross-Site Request Forgery (CSRF) vulnerability in SAP BusinessObjects Business Intelligence Platform. An authenticated user can be tricked into unknowingly sending unintended requests to the web server due to insufficient CSRF protection mechanisms, allowing attackers to perform actions on behalf of legitimate users.

MitigationImplement anti-CSRF tokens for all state-changing operations, validate Origin and Referer headers, and configure SameSite attributes on session cookies to prevent cross-origin request forgery attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

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 installation and version
    Locate the SAP BusinessObjects installation directory (commonly in C:\Program Files\SAP BusinessObjects or /opt/sap bo) and check the version information in the，中央管理工具 or BI platform configuration files.
    Affected if The installed version matches any SAP BusinessObjects BI Platform version that has this CSRF vulnerability.
  2. Confirm web interface is enabled and accessible
    Verify the SAP BusinessObjects Web Application Container (Tomcat or Java) is running and the web portal (typically at /BOE/BI or /.jsp) is accessible over HTTP/HTTPS.
    Affected if The web interface is exposed and users authenticate to the BusinessObjects platform through a browser.
  3. Inspect form submissions for anti-CSRF tokens
    Use browser developer tools to examine HTML forms submitted from the BusinessObjects web portal. Look for hidden input fields containing tokens or check request headers for anti-CSRF token parameters on state-changing operations (like user management, report scheduling, or document publishing).
    Affected if State-changing POST requests lack anti-CSRF token validation (no hidden token field and no custom request header).
  4. Verify session cookie SameSite attribute configuration
    In the SAP BusinessObjects web container configuration (Tomcat server.xml or web.xml), inspect the session cookie configuration. Check for the SameSite attribute being set on JSESSIONID and other session cookies.
    Affected if Session cookies (JSESSIONID) do not have the SameSite attribute set to 'Strict' or 'Lax', or the attribute is missing entirely.
  5. Check Origin and Referer header validation
    Review the web application server logs or proxy configuration to verify if incoming requests are validated against expected Origin or Referer headers for cross-origin requests.
    Affected if The application does not validate Origin or Referer headers, allowing requests from untrusted origins to succeed.

You are affected if SAP BusinessObjects BI Platform web interface is exposed, and state-changing operations lack anti-CSRF token validation and proper SameSite cookie attributes, allowing authenticated users to be exploited via cross-site request forgery.

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

Implement anti-CSRF tokens for all state-changing operations, validate Origin and Referer headers, and configure SameSite attributes on session cookies to prevent cross-origin request forgery attacks.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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