# CVE-2022-31000: CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend

> Attackers can trick administrators into modifying order adjustments via CSRF, requiring an upgrade to the Solidus backend.

- **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-8639-qx56-r428

## What is CVE-2022-31000?

CVE-2022-31000 is a low-severity vulnerability in solidusio solidus, published on 1 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

solidus_backend is the admin interface for the Solidus e-commerce framework. Versions prior to 3.1.6, 3.0.6, and 2.11.16 contain a cross-site request forgery (CSRF) vulnerability. The vulnerability allows attackers to change the state of an order's adjustments if they hold its number, and the execution happens on a store administrator's computer. Users should upgrade to solidus_backend 3.1.6, 3.0.6, or 2.11.16 to receive a patch.

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

## Which versions are affected by CVE-2022-31000?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `solidus_backend` | RubyGems | All versions | 2.11.16 |
| `solidus_backend` | RubyGems | All versions | 2.11.16 |
| `solidus_backend` | RubyGems | From 3.0.0 | 3.0.6 |
| `solidus_backend` | RubyGems | From 3.0.0 | 3.0.6 |
| `solidus_backend` | RubyGems | From 3.1.0 | 3.1.6 |
| `solidus_backend` | RubyGems | From 3.1.0 | 3.1.6 |

Products: Nebulab Solidus.

## How do I fix CVE-2022-31000?

Upgrade solidus_backend to a fixed version for your release line: 2.11.16, 3.0.6 or 3.1.6.

## Is CVE-2022-31000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31000 exists.

## 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-2021-43846](https://insights.sbomify.com/CVE-2021-43846/): CSRF forgery protection bypass for Spree::OrdersController#populate (medium 5.3)
- [CVE-2020-15109](https://insights.sbomify.com/CVE-2020-15109/): Ability to change order address without triggering address validations in solidus (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31000 and fix it if it is affected.

What it is: CVE-2022-31000 is a low-severity vulnerability in solidusio solidus, published on 1 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31000 exists.

Affected packages and fixed versions:
- solidus_backend (RubyGems): affected all versions; fixed in 2.11.16
- solidus_backend (RubyGems): affected all versions; fixed in 2.11.16
- solidus_backend (RubyGems): affected from 3.0.0; fixed in 3.0.6
- solidus_backend (RubyGems): affected from 3.0.0; fixed in 3.0.6
- solidus_backend (RubyGems): affected from 3.1.0; fixed in 3.1.6
- solidus_backend (RubyGems): affected from 3.1.0; fixed in 3.1.6

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-2022-31000/ (Markdown: https://insights.sbomify.com/CVE-2022-31000/index.md)
```

## Sources

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

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