LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36919: Information Disclosure in SAP Enable Now

In SAP Enable Now - versions WPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, ENABLE_NOW_CONSUMP_DEL 1704, the Referrer-Policy response header is not implemented, allowing an unauthenticated attacker to obtain referrer details, resulting in information disclosure.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

SAP Enable Now can expose referrer information because affected versions do not set the Referrer-Policy response header. This is a medium-severity confidentiality issue, not a system takeover. The business concern is unintended leakage of URLs or navigation context that may contain sensitive operational details.

Executive priority

Treat this as a standard vulnerability-management item, not an emergency, unless affected SAP Enable Now URLs contain sensitive identifiers or are internet-exposed. Prioritize verification and SAP guidance review in the next patch cycle.

Technical view

CVE-2023-36919 affects SAP Enable Now WPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, and ENABLE_NOW_CONSUMP_DEL 1704. The issue is missing Referrer-Policy header behavior, mapped to CWE-213. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and no user interaction required.

Likely exposure

Exposure is most relevant where affected SAP Enable Now components are reachable by users or unauthenticated network clients. The source bundle lists default status as unaffected outside the named versions, so version confirmation is essential before prioritizing remediation.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is unauthenticated and remotely reachable, but the documented impact is limited to low confidentiality loss through referrer disclosure.

Researcher notes

Evidence is sufficient for affected products, CVSS, CWE, and vulnerability class. The provided sources do not include SAP Note contents, patch details, workaround specifics, or exploitation evidence, so remediation should be tied to SAP’s official note.

Mitigation direction

  • Review SAP Note 3326769 for official vendor correction or workaround guidance.
  • Confirm whether any deployed SAP Enable Now component matches the affected version list.
  • Apply vendor-provided updates or configuration guidance if SAP identifies required action.
  • Where supported, enforce an appropriate Referrer-Policy at the application or edge layer.
  • Limit public exposure of affected SAP Enable Now services where business requirements allow.

Validation and detection

  • Inventory SAP Enable Now deployments and record exact product/version identifiers.
  • Check representative HTTP responses for a Referrer-Policy header.
  • Verify affected-version systems are covered by SAP Note 3326769 guidance.
  • After remediation, confirm the expected header is consistently returned.
  • Review whether URLs contain sensitive data that could amplify referrer leakage.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-213: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-36919 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-36919Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SAP_SESAP Enable NowWPB_MANAGER 1.0, WPB_MANAGER_CE 10, WPB_MANAGER_HANA 10, ENABLE_NOW_CONSUMP_DEL 1704unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-213 · source CWE mapping

Exposure of Sensitive Information Due to Incompatible Policies

Exposure of Sensitive Information Due to Incompatible Policies represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.