dbcve.org
Open RedirectWeakness · CWE-601

CVE-2025-42985

MEDIUM · 6.1 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 sanitization in the SAP BusinessObjects Content Administrator Workbench, attackers could craft malicious URLs and execute scripts in a victim�s browser. This could potentially lead to the exposure or modification of web client data, resulting in low impact on confidentiality and integrity, with no impact on application 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

This is a reflected cross-site scripting (XSS) vulnerability in SAP BusinessObjects Content Administrator Workbench. Due to insufficient input sanitization, attackers can craft malicious URLs containing script payloads that execute in the context of a victim's browser session, potentially leading to session hijacking or data exposure.

MitigationApply the relevant SAP security patch for CVE-2025-42985 and implement proper input validation and output encoding in the Content Administrator Workbench to prevent XSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Identify SAP BusinessObjects installation and version
    Check the SAP BusinessObjects installation directory or use system inventory tools to locate the BusinessObjects enterprise application and retrieve its version number. Compare against any available SAP security notes for CVE-2025-42985.
    Affected if The installed version falls within the affected version range for this CVE.
  2. Confirm Content Administrator Workbench is enabled
    Locate the Content Administrator Workbench module configuration in the SAP BusinessObjects Central Management Console (CMC) or the web.xml deployment descriptor. Verify the module status is set to 'enabled' or is accessible.
    Affected if The Content Administrator Workbench module is enabled and accessible to users.
  3. Verify web interface accessibility
    Determine if the SAP BusinessObjects web application server (typically Tomcat or similar) is listening on HTTP/HTTPS ports. Check the network configuration to confirm the CMC and Content Administrator Workbench URLs are reachable from user browsers.
    Affected if The Content Administrator Workbench web interface is exposed over the network without proper access restrictions.
  4. Inspect Content Administrator Workbench URL parameters
    Access the Content Administrator Workbench through the SAP BusinessObjects web interface. Navigate through the interface and examine the URL structure for any user-controllable parameters (look for query string parameters in URLs ending in .do, .jsp, or similar).
    Affected if The URLs contain unsanitized parameters that could be manipulated with script payloads.
  5. Review web server logs for XSS probe attempts
    Examine the SAP BusinessObjects web container access logs (typically found in the logs or tomcat directory) for suspicious request patterns involving script tags or HTML in URL parameters targeting the Content Administrator Workbench endpoints.
    Affected if Malicious XSS payloads have already been observed in logs targeting this component.

A user is affected if SAP BusinessObjects with the Content Administrator Workbench module is running and accessible, and the installed version matches the affected range for CVE-2025-42985.

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 CVE-2025-42985 and implement proper input validation and output encoding in the Content Administrator Workbench to prevent XSS attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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