# CVE-2021-43846: CSRF forgery protection bypass for Spree::OrdersController#populate

> Attackers can add items to a user's cart without consent via CSRF, affecting Solidus e-commerce storefronts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h3fg-h5v3-vf8m

## What is CVE-2021-43846?

CVE-2021-43846 is a medium-severity vulnerability in solidusio solidus, published on 20 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`solidus_frontend` is the cart and storefront for the Solidus e-commerce project. Versions of `solidus_frontend` prior to 3.1.5, 3.0.5, and 2.11.14 contain a cross-site request forgery (CSRF) vulnerability that allows a malicious site to add an item to the user's cart without their knowledge. Versions 3.1.5, 3.0.5, and 2.11.14 contain a patch for this issue. The patch adds CSRF token verification to the "Add to cart" action. Adding forgery protection to a form that missed it can have some side effects. Other CSRF protection strategies as well as a workaround involving modifcation to config/application.rb` are available. More details on these mitigations are available in the GitHub Security Advisory.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-43846?

6 open source packages ship an affected version, including solidus_frontend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `solidus_frontend` | RubyGems | All versions | 2.11.14 |
| `solidus_frontend` | RubyGems | All versions | 2.11.14 |
| `solidus_frontend` | RubyGems | From 3.0.0 | 3.0.5 |
| `solidus_frontend` | RubyGems | From 3.0.0 | 3.0.5 |
| `solidus_frontend` | RubyGems | From 3.1.0 | 3.1.5 |
| `solidus_frontend` | RubyGems | From 3.1.0 | 3.1.5 |

Products: Nebulab Solidus.

## How do I fix CVE-2021-43846?

Upgrade solidus_frontend to a fixed version for your release line: 2.11.14, 3.0.5 or 3.1.5.

## Is CVE-2021-43846 being exploited?

There is no known exploitation of CVE-2021-43846 in the wild and no public exploit code.

## Other vulnerabilities in solidusio solidus

- [CVE-2021-43805](https://insights.sbomify.com/CVE-2021-43805/): ReDos vulnerability on guest checkout email validation (high 7.5)
- [CVE-2020-15109](https://insights.sbomify.com/CVE-2020-15109/): Ability to change order address without triggering address validations in solidus (medium 5.3)
- [CVE-2022-31000](https://insights.sbomify.com/CVE-2022-31000/): CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend (low 2.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43846 and fix it if it is affected.

What it is: CVE-2021-43846 is a medium-severity vulnerability in solidusio solidus, published on 20 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43846 in the wild and no public exploit code.

Affected packages and fixed versions:
- solidus_frontend (RubyGems): affected all versions; fixed in 2.11.14
- solidus_frontend (RubyGems): affected all versions; fixed in 2.11.14
- solidus_frontend (RubyGems): affected from 3.0.0; fixed in 3.0.5
- solidus_frontend (RubyGems): affected from 3.0.0; fixed in 3.0.5
- solidus_frontend (RubyGems): affected from 3.1.0; fixed in 3.1.5
- solidus_frontend (RubyGems): affected from 3.1.0; fixed in 3.1.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-43846/ (Markdown: https://insights.sbomify.com/CVE-2021-43846/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43846
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43846
- OSV: https://osv.dev/vulnerability/CVE-2021-43846

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43846/
Summaries are generated and may contain mistakes; the official description above is the record.