dbcve.org
MagentoCMS

CVE-2019-7864

MEDIUM · 5.3 CVSS v3.0 Published 2019-08-02
Fix available
A fix is available. Upgrade to 2.1.18 / 2.2.9 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
An insecure direct object reference (IDOR) vulnerability exists in the RSS feeds of Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This can lead to unauthorized access to order details.

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 confidence

An IDOR vulnerability in Magento 2's RSS feeds allows authenticated users to access order details belonging to other users by manipulating object references in RSS feed requests, leading to unauthorized disclosure of sensitive order information.

MitigationUpgrade Magento 2 to version 2.1.18, 2.2.9, 2.3.2 or later, which contain proper authorization validation for RSS feed endpoints preventing unauthorized order access.

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.1.0, < 2.1.18>= 2.2.0, < 2.2.9>= 2.3.0, < 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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Magento 2 version
    Run 'php bin/magento --version' from the Magento installation directory, or inspect the 'composer.json' file for the 'version' field under 'extra' section
    Affected if The version displayed falls within the affected ranges: >= 2.1.0 and < 2.1.18, >= 2.2.0 and < 2.2.9, or >= 2.3.0 and < 2.3.2
  2. Verify RSS feed module is enabled
    Run 'php bin/magento module:status | grep -i rss' or check the admin panel under Stores > Configuration > Advanced > Advanced to confirm the Magento_Rss module is enabled
    Affected if The Magento_Rss module is in the list of enabled modules (not listed as disabled)
  3. Check RSS feed configuration settings
    Log into the Magento admin panel and navigate to Stores > Configuration > Catalog > RSS Feed, or inspect the core_config_data table in the database for paths starting with 'rss/'
    Affected if RSS feeds are enabled at the system or website level in the configuration

A user is affected if their Magento 2 version falls within the vulnerable ranges AND the RSS module is enabled and accessible to authenticated users.

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.1.18 / 2.2.9 / 2.3.2 or later
Fixed in 2.1.182.2.92.3.2
Interim mitigation

Upgrade Magento 2 to version 2.1.18, 2.2.9, 2.3.2 or later, which contain proper authorization validation for RSS feed endpoints preventing unauthorized order access.

Fix this in Magento Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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