dbcve.org
Enable NowApplication · Sap

CVE-2019-0403

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-11
Fix available
A fix is available. Upgrade to 1911 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 1911, allows an attacker to input commands into the CSV files, which will be executed when opened, leading to CSV Command Injection.

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 CSV Command Injection vulnerability in SAP Enable Now where attackers can embed malicious commands/formulas into CSV files. When users open these specially crafted CSV files in spreadsheet applications, the embedded commands can be automatically executed on the victim's system, potentially leading to remote code execution. The vulnerability affects versions prior to 1911.

MitigationUpgrade SAP Enable Now to version 1911 or later to remediate this vulnerability. Additionally, implement user awareness training to avoid opening untrusted CSV files from external or unknown sources until the patch is applied.

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:< 1911

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate SAP Enable Now installation
    Check common installation directories such as C:\Program Files\SAP\Enable Now or C:\Program Files (x86)\SAP\Enable Now on Windows, or /opt/sap/enable_now on Linux. Also check for desktop shortcuts or the Start menu for SAP Enable Now entries.
    Affected if SAP Enable Now is not found on the system, the product is not installed.
  2. Determine installed version
    Navigate to the SAP Enable Now installation directory and locate a version file, about dialog, or check the application executable properties (right-click the main .exe file and select Properties, then view the Details tab for Version information).
    Affected if The version displayed is lower than 1911 (for example, 1905, 10.x, or any version number below 1911).
  3. Identify CSV file handling usage
    Review the SAP Enable Now configuration or documentation to determine if the content creation or file import features that handle CSV files are in use. Check the manager client or author client for imported or created content that includes CSV data sources.
    Affected if Users have the ability to import or create CSV-based content within SAP Enable Now, enabling the attack surface for malicious CSV file processing.
  4. Verify user access to CSV file processing
    Examine user roles and permissions in the SAP Enable Now manager to identify which users can access CSV file import or content creation features. Review any workflows that involve external CSV file uploads or conversions.
    Affected if Non-administrator or external users have permissions to upload or process CSV files through the SAP Enable Now platform.

The environment is affected if SAP Enable Now is installed with a version number lower than 1911 and users have the ability to import or process CSV files through the application.

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.

dbcve · scoped
Upgrade available Upgrade to 1911 or later
Fixed in 1911
Interim mitigation

Upgrade SAP Enable Now to version 1911 or later to remediate this vulnerability. Additionally, implement user awareness training to avoid opening untrusted CSV files from external or unknown sources until the patch is applied.

Recommended fix High confidence

SAP Enable Now version 1911 or later

  1. Identify the current version of SAP Enable Now deployed in your environment
  2. Review SAP Enable Now 1911 release notes and upgrade prerequisites
  3. Plan and schedule a maintenance window for the upgrade
  4. Perform a backup of current SAP Enable Now data and configuration
  5. Execute the upgrade to version 1911 or later following SAP's official upgrade guide
  6. Verify the upgrade was successful by checking the version number
  7. Test CSV file functionality to confirm the command injection vulnerability is remediated
  8. Apply any additional recommended security settings from SAP

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enable Now Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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