dbcve.org
MagentoCMS

CVE-2019-7939

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-02
Fix available
A fix is available. Upgrade to 2.1.18 / 2.2.9 or later.
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
A reflected cross-site scripting vulnerability exists on the customer cart checkout page of Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This could be exploited by sending a victim a crafted URL that results in malicious javascript execution in the victim's browser.

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

Reflected cross-site scripting vulnerability in Magento 2's customer cart checkout page allows attackers to inject malicious JavaScript via crafted URLs. The attack requires tricking users into clicking a specially constructed link.

MitigationApply the appropriate Magento security patch or upgrade to version 2.1.18, 2.2.9, 2.3.2 or later to resolve the vulnerability.

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
MagentoCMS
Affected:>= 2.1.0, < 2.1.18>= 2.2.0, < 2.2.9>= 2.3.0, < 2.3.2

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.0/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 Magento version
    Run the Magento CLI command to retrieve the current version, such as bin/magento --version or check composer.json for the magento/product-community-edition version
    Affected if The version is >= 2.1.0 and < 2.1.18, OR >= 2.2.0 and < 2.2.9, OR >= 2.3.0 and < 2.3.2
  2. Verify checkout functionality is enabled
    Attempt to access the customer cart or checkout URL path on the storefront, such as /checkout/cart or /checkout
    Affected if The page loads without being blocked, indicating the checkout module is active
  3. Confirm storefront is in production mode
    Check that the Magento application is not in developer or maintenance mode, which would limit public exposure
    Affected if The storefront is live and accessible to customers, making the XSS vector exploitable

Your environment is affected if the installed Magento version falls within the vulnerable ranges AND the checkout page is publicly accessible.

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 2.1.18 / 2.2.9 / 2.3.2 or later
Fixed in 2.1.182.2.92.3.2
Interim mitigation

Apply the appropriate Magento security patch or upgrade to version 2.1.18, 2.2.9, 2.3.2 or later to resolve the vulnerability.

Fix this in Magento Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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