dbcve.org
MagentoCMS

CVE-2019-8127

HIGH · 8.8 CVSS v3.1 Published 2019-11-05
Fix available
A fix is available. Upgrade to 2.2.10 / 2.3.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A SQL injection vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user with privileges to an account with Newsletter Template editing permission could exfiltrate the Admin login data, and reset their password, effectively performing a privilege escalation.

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

SQL injection vulnerability in Magento 2.2 prior to 2.2.10 and 2.3 prior to 2.3.3/2.3.2-p1 in the Newsletter Template editing feature. An authenticated user with Newsletter Template editing permissions can inject malicious SQL queries to exfiltrate Admin login credentials and reset admin passwords, achieving privilege escalation.

MitigationApply the official Magento security patches or upgrade to Magento 2.2.10, 2.3.3, or 2.3.2-p1 or later. Additionally, review user permissions and audit admin accounts for unauthorized changes.

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.2.0, < 2.2.10>= 2.3.0, < 2.3.2= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed Magento version
    Run 'php bin/magento --version' from the Magento root directory, or log into the Admin panel and check System > Configuration > Advanced > Developer > Version (or check the composer.json file for the 'version' field)
    Affected if The version is >= 2.2.0 and < 2.2.10, OR >= 2.3.0 and <= 2.3.2 (including 2.3.2)
  2. Verify Newsletter module is enabled
    Run 'php bin/magento module:status Magento_Newsletter' or check via Admin > Stores > Configuration > Advanced > Advanced > Disable Modules Output to confirm the Newsletter module is not disabled
    Affected if The Newsletter module is installed and enabled (the vulnerability exists in this component)
  3. Confirm user has Newsletter Template editing permissions
    Review user roles in Admin > System > Permissions > User Roles and check if the role includes 'Newsletter Template' resource under the Newsletter section (or check the admin_role and admin_rule database tables for permissions on newsletter_template)
    Affected if An authenticated admin user has the Newsletter Template editing permission assigned to their role
  4. Audit admin account changes
    Check the admin_user table for any recent password changes, or review the admin_users and admin_session tables for unauthorized access patterns; also check System > Actions Log > Report for login anomalies around the time of potential exploitation
    Affected if There are unexpected admin password changes or unauthorized admin sessions that may indicate the vulnerability was exploited

You are affected if your Magento version falls within 2.2.0-2.2.9 or 2.3.0-2.3.2, the Newsletter module is enabled, and an authenticated user with Newsletter Template editing permissions exists in your environment.

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.2.10 / 2.3.2 or later
Fixed in 2.2.102.3.2
Interim mitigation

Apply the official Magento security patches or upgrade to Magento 2.2.10, 2.3.3, or 2.3.2-p1 or later. Additionally, review user permissions and audit admin accounts for unauthorized changes.

Fix this in Magento Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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