dbcve.org
CommerceApplication · Adobe

CVE-2021-39864

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-15
Fix available
A fix is available. Upgrade to after 2.3.7 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Adobe Commerce versions 2.4.2-p2 (and earlier), 2.4.3 (and earlier) and 2.3.7p1 (and earlier) are affected by a cross-site request forgery (CSRF) vulnerability via a Wishlist Share Link. Successful exploitation could lead to unauthorized addition to customer cart by an unauthenticated attacker. Access to the admin console is not required for successful exploitation.

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

Adobe Commerce contains a CSRF vulnerability in the Wishlist Share Link functionality. An unauthenticated attacker can craft a malicious link that, when clicked by an authenticated user, forces the user's browser to add items to their cart without consent. The vulnerability stems from missing anti-CSRF token validation on wishlist-related cart operations.

MitigationImplement anti-CSRF tokens (form keys) on all wishlist-related actions that modify the cart. Additionally, validate request origin/referer headers and consider implementing SameSite cookie attributes to further mitigate CSRF attacks.

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
CommerceApplication
Affected:<= 2.3.7= 2.3.7= 2.4.2= 2.4.3
Magento Open SourceApplication
Affected:<= 2.3.7= 2.3.7= 2.4.2= 2.4.3

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

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

  1. Check Adobe Commerce or Magento Open Source version
    Run the CLI command: php bin/magento --version or check the composer.json file for the version entry
    Affected if Installed version is 2.3.7 or earlier, or exactly 2.4.2 or 2.4.3
  2. Verify Wishlist module is enabled
    Run: php bin/magento module:status Magento_Wishlist or check app/etc/config.php for Magento_Wishlist = 1
    Affected if The Wishlist module is active/enabled in the installation
  3. Inspect wishlist cart action for form key validation
    Examine the controller handling wishlist-to-cart operations (typically in vendor/magento/module-wishlist/Controller/Index/Cart.php or similar) and check if form key (form_key) is validated in the post data
    Affected if The controller action does not validate the form_key parameter from the request
  4. Check wishlist template for form key inclusion
    Inspect the wishlist templates that render 'Add to Cart' buttons (usually in vendor/magento/module-wishlist/view/frontend/templates/catalog/product/view/addto/wishlist.phtml or similar) for presence of $block->getBlock('form.key') or similar form key output
    Affected if The wishlist 'Add to Cart' buttons do not include a form key token in the rendered HTML
  5. Review wishlist AJAX cart endpoints
    Check any AJAX endpoints used by wishlist cart operations (typically in vendor/magento/module-wishlist/Controller/Index/Ajax or similar) for CSRF token validation logic
    Affected if The AJAX cart endpoints lack referer header validation or CSRF token checks

A user is affected if they run an affected Adobe Commerce or Magento Open Source version (2.3.7 or earlier, 2.4.2, or 2.4.3) with the Wishlist module enabled and wishlist cart actions lack form key validation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3.7
Interim mitigation

Implement anti-CSRF tokens (form keys) on all wishlist-related actions that modify the cart. Additionally, validate request origin/referer headers and consider implementing SameSite cookie attributes to further mitigate CSRF attacks.

Recommended fix High confidence

Adobe Commerce/Magento Open Source 2.4.3-p1+ or 2.4.2-p3+ or 2.3.7p2+

  1. 1. Verify current Magento installation version by running: bin/magento --version or checking composer.json
  2. 2. Create a full backup of the database and files before proceeding with the upgrade
  3. 3. For Adobe Commerce (Magento Commerce) users: Upgrade to version 2.4.3-p1 or later, or 2.4.2-p3 or later, or 2.3.7p2 or later
  4. 4. For Magento Open Source users: Apply the corresponding security patch (if available) or upgrade to the equivalent patched version
  5. 5. Clear Magento cache after upgrade: bin/magento cache:clean && bin/magento cache:flush
  6. 6. Reindex if necessary: bin/magento indexer:reindex
  7. 7. Verify the fix by testing the Wishlist share functionality to confirm CSRF protection is in place
Caveat Standard Magento upgrade risks apply - test thoroughly in staging first, as custom extensions may require compatibility updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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