CVE-2019-7889
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 · uneditedAn injection vulnerability exists in Magento Open Source prior to 1.9.4.2, and Magento Commerce prior to 1.14.4.2, Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. An authenticated user with marketing manipulation privileges can invoke methods that alter data of the underlying model followed by corresponding database modifications.
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 · moderate confidenceA model-level injection vulnerability in Magento allows authenticated users with marketing manipulation privileges to invoke methods that alter underlying model data, leading to unauthorized database modifications. This could enable data manipulation or privilege escalation within the e-commerce platform.
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< 1.9.4.2< 1.14.4.2>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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.
-
Identify Magento installation versionCheck the version.php file in your Magento root or bin/magento --version command output. For Magento 1, check app/Mage.php. For Magento 2, check composer.json or run 'bin/magento --version'.Affected if The installed version falls below 1.9.4.2 or 1.14.4.2 (M1), or is below 2.1.18, 2.2.9, or 2.3.2 (M2).
-
Verify user authentication is accessibleDetermine whether the website allows user registration or has active user accounts. Check if the customer account creation functionality is enabled in the admin panel under Stores > Configuration > Customers > Customer Configuration > Allow Customer Registration.Affected if User registration or existing user accounts are present, providing a potential attack vector for authenticated exploitation.
-
Confirm marketing module statusCheck if Magento's marketing-related functionality is accessible. In Magento 2, verify the presence of marketing modules via bin/magento module:status. In Magento 1, check app/etc/modules/ for marketing-related extensions.Affected if Marketing modules are enabled and accessible to authenticated users with marketing privileges.
-
Audit admin user accountsReview the admin_user table in the database or check Admin > System > All Users (Magento 1) or System > Permissions > All Users (Magento 2) for unauthorized or unexpected administrator accounts.Affected if Unexpected admin accounts exist that may have been created through exploitation of this vulnerability.
-
Inspect for suspicious model data changesReview database tables for unexpected modifications, particularly in customer, order, or product-related models. Check admin_action_log or similar audit tables for unusual model manipulation events.Affected if Model-level data changes are present that were not initiated through legitimate admin operations.
You are affected if your Magento installation version is within the vulnerable ranges AND authenticated user access (particularly with marketing privileges) is possible or was compromised.
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 data1.9.4.21.14.4.22.1.18
Apply the appropriate Magento security patch or upgrade to the fixed versions (Open Source/Commerce 1.9.4.2+, 1.14.4.2+, 2.1.18+, 2.2.9+, or 2.3.2+) to remediate this injection vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7889 — 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-7889 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