dbcve.org
Enable Now Enable Now Consump DelApplication · Sap

CVE-2023-36920

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-30
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
In SAP Enable Now - versions WPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, ENABLE_NOW_CONSUMP_DEL 1704, the X-FRAME-OPTIONS response header is not implemented, allowing an unauthenticated attacker to attempt clickjacking, which could result in disclosure or modification of information.

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

SAP Enable Now web applications across multiple versions (WPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, ENABLE_NOW_CONSUMP_DEL 1704) do not implement the X-FRAME-OPTIONS HTTP response header, allowing the application to be embedded in iframes. This enables clickjacking attacks where attackers overlay the legitimate interface with invisible frames to trick authenticated users into performing unintended actions.

MitigationConfigure the web server or application to include the X-FRAME-OPTIONS header (preferably DENY or SAMEORIGIN) in all HTTP responses, or implement Content-Security-Policy with frame-ancestors directive as a modern alternative.

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
Enable Now Enable Now Consump DelApplication
Affected:= 1704
Enable Now Wpb ManagerApplication
Affected:= 1.0
Enable Now Wpb Manager CeApplication
Affected:= 10
Enable Now Wpb Manager HanaApplication
Affected:= 10

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 installed SAP Enable Now version
    Locate the SAP Enable Now installation directory or check the product version through the administration console. Look for version files or check the 'About' section in WPB_MANAGER, WPB_MANAGER_CE, WPB_MANAGER_HANA, or ENABLE_NOW_CONSUMP_DEL components.
    Affected if The installed version matches exactly 1.0 for WPB_MANAGER, 10 for WPB_MANAGER_CE, 10 for WPB_MANAGER_HANA, or 1704 for ENABLE_NOW_CONSUMP_DEL.
  2. Verify web application is accessible
    Confirm the SAP Enable Now web application is reachable over HTTP/HTTPS by accessing its URL endpoint through a browser or curl command.
    Affected if The web application is publicly or internally accessible over the network.
  3. Check for missing X-FRAME-OPTIONS header
    Use a browser developer tool, curl -I, or a header inspection tool to capture the HTTP response headers from the SAP Enable Now web application homepage and any authenticated endpoints. Look specifically for the X-FRAME-OPTIONS header.
    Affected if The HTTP response does not contain the X-FRAME-OPTIONS header, or the header is present but set to a permissive value such as ALLOW-FROM (non-SAMEORIGIN/DENY values).
  4. Check for Content-Security-Policy frame-ancestors
    Inspect the HTTP response headers for a Content-Security-Policy header that includes the frame-ancestors directive as an alternative mitigation.
    Affected if Neither X-FRAME-OPTIONS header nor Content-Security-Policy with frame-ancestors directive is present in the HTTP responses.

A user is affected if the SAP Enable Now web application version matches 1.0, 10, or 1704 AND the HTTP responses lack X-FRAME-OPTIONS DENY/SAMEORIGIN or equivalent CSP frame-ancestors protection, allowing the application to be embedded in iframes.

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

Configure the web server or application to include the X-FRAME-OPTIONS header (preferably DENY or SAMEORIGIN) in all HTTP responses, or implement Content-Security-Policy with frame-ancestors directive as a modern alternative.

Fix this in Enable Now Enable Now Consump Del Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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