CSRF forgery protection bypass in solidus_frontend

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2021-43846: 0.59% estimated exploitation activity in the next 30 days; percentile 48.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact CSRF vulnerability that allows a malicious site to add an item to the user's cart without their knowledge. All solidusfrontend versions are affected. If you're using your own storefront, please, follow along to make sure you're not affected. To reproduce the issue: - Pick the id for a variant with available stock. From the rails console: Say we pick variant id 2. - Launch your application, for instance, on http://localhost:3000: - Open your browser dev tools. - Click on whatever link in your store. - Copy the value of the Cookie request header sent for the previous request from your browser dev tools. - Execute the following, using your previously selected variant id and the value of the Cookie header (notice how it doesn't contain any authentication token): - Reload your browser and look at how your cart got updated. Patches Please, upgrade solidus to versions 3.1.5, 3.0.5 or 2.11.14. After upgrading, make sure you read the "Upgrade notes" section below. Upgrade notes The…

Published by the source

6 Jan 2022, 18:33 UTC

Last modified by the source

4 May 2023, 19:59 UTC

Source last checked

26 Oct 2026, 15:47 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h3fg-h5v3-vf8m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-43846

Advisory: CSRF forgery protection bypass in solidus_frontend
IDs: CVE-2021-43846, GHSA-h3fg-h5v3-vf8m
Record: https://patchnext.com/advisories/cve-2021-43846 (revision 1, source checked 26 Oct 2026, 15:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: solidus_frontend 3.1.5, 3.0.5, 2.11.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems solidus_frontend: affected < 2.11.14; >= 3.0.0, < 3.0.5; >= 3.1.0, < 3.1.5; fixed in 3.1.5, 2.11.14, 3.0.5

## Suggested inspection (read-only)
- RubyGems solidus_frontend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on solidus_frontend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h3fg-h5v3-vf8m (GitHub-reviewed advisory GHSA-h3fg-h5v3-vf8m lists affected ranges: RubyGems solidus_frontend >=0 =3.0.0 =3.1.0 <3.1.5)

Commands are suggestions: review each one before running it.