CVE-2019-7851
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 · uneditedA cross-site request forgery vulnerability in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2 can lead to unintended data deletion from customer pages.
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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in Magento 2.x e-commerce platform versions prior to 2.1.18, 2.2.9, and 2.3.2. The vulnerability allows attackers to trick authenticated users into unknowingly submitting requests that cause unintended data deletion from customer-facing pages.
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>= 2.1.0, < 2.1.18>= 2.2.0, < 2.2.9>= 2.3.0, < 2.3.2CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Magento versionRun the command 'php bin/magento --version' from the Magento installation directory, or check the 'composer.json' file for the 'version' field in the root of your Magento installation.Affected if The installed version falls within these ranges: >= 2.1.0 and < 2.1.18, OR >= 2.2.0 and < 2.2.9, OR >= 2.3.0 and < 2.3.2
-
Confirm user authentication is enabledVerify that the Magento instance has customer account functionality enabled. Check the admin panel under 'Stores > Configuration > Customers > Customer Configuration > Account Options' to confirm customer registration and login are allowed, or inspect the 'customer_account_create' XML layout files in the theme.Affected if Customer-facing authentication is enabled, meaning users can log in to the storefront.
-
Verify delete functionality exists on customer pagesReview custom modules or theme overrides that add delete operations (for items such as wishlist items, address book entries, or review submissions) on customer-facing pages. Check for form actions performing DELETE or POST requests without anti-CSRF token validation in the frontend templates.Affected if Custom or third-party modules expose delete operations on customer-facing pages without proper CSRF token validation.
You are affected if your Magento 2 installation version is 2.1.0-2.1.17, 2.2.0-2.2.8, or 2.3.0-2.3.1 AND you have customer authentication enabled with delete operations on storefront pages.
Generated from the published advisory. Verify against your own configuration.
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 data2.1.182.2.92.3.2
Apply the relevant Magento security patch (SUPEE-10888 or corresponding version-specific patches) to add anti-CSRF token validation for delete operations on customer pages. Alternatively, upgrade to a patched version of Magento.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7851 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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