CVE-2019-7849: A defense-in-depth check was added to mitigate inadequate session validation handling by 3rd party checkout modules.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: magento/community-edition (Packagist) 2.1.18, 2.2.9, 2.3.2.
Low priority for now. Upgrade to magento/community-edition (Packagist) 2.1.18, 2.2.9, 2.3.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A defense-in-depth check was added to mitigate inadequate session validation handling by 3rd party checkout modules. This impacts Magento 1.x prior to 1.9.4.2, Magento Commerce prior to 1.14.4.2, Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9 and Magento 2.3 prior to 2.3.2.
- Published
- Aug 2, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-384
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| magento | magento | cpe:2.3:a:magento:magento |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.
n/a Magento 1 Magento 2
- 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.2affected
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- magento magentobefore 1.14.4.2
- magento magento1.0.0 and later · before 1.9.4.2
- magento magento2.1.0 and later · before 2.1.18
- magento magento2.2.0 and later · before 2.2.9
- magento magento2.3.0 and later · before 2.3.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | magento/community-edition | from 2.1.0 · before 2.1.18 | 2.1.18 |
| Packagist | magento/community-edition | from 2.2.0 · before 2.2.9 | 2.2.9 |
| Packagist | magento/community-edition | from 2.3.0 · before 2.3.2 | 2.3.2 |
Same product
magento: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-4010Magento CE and EE before 2.0.6 allows remote attackers to conduct PHP objection injection attacks and execute arbitrary PHP code via…67This week
- CVE-2019-7139An unauthenticated user can execute SQL statements that allow arbitrary read access to the underlying database, which causes sensitive data…46Plan
- CVE-2021-21029Magento Commerce Reflected Cross-site Scripting Vulnerability Could Lead To Arbitrary JavaScript Execution45Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-10704Dec 30, 2017 · Magento Community Edition and Enterprise Edition before 2.0.10 and 2.1.x before 2.1.2 have XSS via e-mail templates that are mishandled…24Monitor
- ← EarlierCVE-2018-5301Jan 8, 2018 · Magento Community Edition and Enterprise Edition before 2.0.10 and 2.1.x before 2.1.2 have CSRF resulting in deletion of a customer address…26Monitor
- Later →CVE-2019-7851Aug 2, 2019 · A 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…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:magento/community-edition | 2.1.18 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.2.9 | Package registry (OSV) |
| Packagist:magento/community-edition | 2.3.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-384 · Session FixationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session Credential Falsification through ForgingCAPEC-196likelihood: Medium · Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
- Session FixationCAPEC-61likelihood: Medium · High
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Access Token Manipulation: Create Process with TokenT1134.002
- Access Token Manipulation: Make and Impersonate TokenT1134.003
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Forge Web CredentialsT1606
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.