dbcve.org
Enable NowApplication · Sap

CVE-2019-0385

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-13
Fix available
A fix is available. Upgrade to 1908 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 Enable Now, before version 1908, does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability.

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 before version 1908 fails to properly encode user-supplied input, allowing attackers to inject malicious scripts via XSS that execute in the browsers of other users who view the content.

MitigationUpgrade SAP Enable Now to version 1908 or later to obtain the patch that implements proper input encoding. If immediate patching is not feasible, implement output encoding at points where user input is rendered and consider deploying a WAF rule to block XSS attempts.

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 NowApplication
Affected:< 1908

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Confirm SAP Enable Now installation
    Locate SAP Enable Now installation directory or identify the running service in your environment
    Affected if SAP Enable Now is installed and running
  2. Identify installed version
    Check the version of SAP Enable Now by accessing the product's about section, version info in the installation directory, or administrative console
    Affected if Version is below 1908 (e.g., 1907, 1905, earlier versions)
  3. Verify web interface accessibility
    Determine if the SAP Enable Now web portal or content viewer is accessible to users over HTTP/HTTPS
    Affected if The web interface is exposed and users can view or submit content
  4. Check user content submission feature
    Confirm that the functionality allowing users to create, edit, or view content within SAP Enable Now is enabled and accessible
    Affected if Users can submit or view user-generated content in the application

You are affected if SAP Enable Now is running with a version number lower than 1908 and the web-based content viewing or submission features are accessible to users.

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
Upgrade available Upgrade to 1908 or later
Fixed in 1908
Interim mitigation

Upgrade SAP Enable Now to version 1908 or later to obtain the patch that implements proper input encoding. If immediate patching is not feasible, implement output encoding at points where user input is rendered and consider deploying a WAF rule to block XSS attempts.

Fix this in Enable Now Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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