Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Magento 2 Community Edition versions 2.1.0 to before 2.1.18, 2.2.0 to before 2.2.9, and 2.3.0 to before 2.3.2 are affected. An authenticated user with marketing manipulation privileges can invoke methods that alter underlying model data and trigger corresponding database changes. Upgrade to 2.1.18, 2.2.9, or 2.3.2, depending on your release line.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.0 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0080, the 57th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:32 UTC First seen by agentprime
- 31 Oct 2026, 14:32 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-hxmp-jcqj-83hm
- OSV: GHSA-hxmp-jcqj-83hm
- nvd.nist.gov/vuln/detail/CVE-2019-7889
- github.com/FriendsOfPHP/security-advisories/blob/master/magento/magento1ce/CVE-2019-7889.yaml
- github.com/FriendsOfPHP/security-advisories/blob/master/magento/magento1ee/CVE-2019-7889.yaml
- github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2019-7889.yaml
- github.com/magento/magento2
- magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13