What is CVE-2022-31000?

CVE-2022-31000 is a low-severity cross-site request forgery (CSRF) vulnerability in solidus_backend (rubygems), affecting versions < 2.11.16. It is fixed in 2.11.16, 3.0.6, 3.1.6. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.

How severe is CVE-2022-31000?

CVE-2022-31000 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of solidus_backend are affected by CVE-2022-31000?

solidus_backend (rubygems) versions < 2.11.16 is affected.

Is there a fix for CVE-2022-31000?

Yes. CVE-2022-31000 is fixed in 2.11.16, 3.0.6, 3.1.6. Upgrade to this version or later.

Is CVE-2022-31000 exploitable, and should I be worried?

Whether CVE-2022-31000 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-31000 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-31000?

Upgrade: solidus_backend to 2.11.16 or later, solidus_backend to 3.0.6 or later, solidus_backend to 3.1.6 or later.

CVE-2022-31000 in solidus_backend

Q: How severe is CVE-2022-31000?

CVE-2022-31000 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of solidus_backend are affected by CVE-2022-31000?

solidus_backend (rubygems) versions < 2.11.16 is affected.

Q: Is there a fix for CVE-2022-31000?

Yes. CVE-2022-31000 is fixed in 2.11.16, 3.0.6, 3.1.6. Upgrade to this version or later.

Q: Is CVE-2022-31000 exploitable, and should I be worried?

Whether CVE-2022-31000 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-31000 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-31000?

Upgrade: solidus_backend to 2.11.16 or later, solidus_backend to 3.0.6 or later, solidus_backend to 3.1.6 or later.

Summary

CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend

References

Rails CSRF protection.

For more information

If you have any questions or comments about this advisory:

Open an issue or a discussion in Solidus.
Email us at [email protected]
Contact the core team on Slack

Impact

CSRF vulnerability allowing 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.

Reproduction steps:

Take an order's number.
Log in as an administrator.
Visit that order's adjustments section (Orders -> {Click on number} -> Adjustments) and check that its adjustments are finalized (closed padlock under the State column).
On another tab, visit {your_site_url}/admin/orders/{order_number}/adjustments/unfinalize.
Notice how the adjustments are unfinalized (open padlock), even if the previous was a GET request which could have been linked from any other site.
Visit {your_site_url}/admin/orders/{order_number}/adjustments/finalize.
Notice how the adjustments are again finalized.

That happened because both routes were handled as GET requests, which are skipped by Rails anti-forgery protection.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2022-31000 has a CVSS score of 2.3 (Low). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.16, 3.0.6, 3.1.6); upgrading removes the vulnerable code path.

Affected versions

solidus_backend (< 2.11.16) solidus_backend (>= 3.0.0, < 3.0.6) solidus_backend (>= 3.1.0, < 3.1.6)

Security releases

solidus_backend → 2.11.16 (rubygems) solidus_backend → 3.0.6 (rubygems) solidus_backend → 3.1.6 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Users should upgrade to solidus_backend v3.1.6, v3.0.6, or v2.11.16, depending on the major and minor versions in use.

Frequently Asked Questions

What is CVE-2022-31000? CVE-2022-31000 is a low-severity cross-site request forgery (CSRF) vulnerability in solidus_backend (rubygems), affecting versions < 2.11.16. It is fixed in 2.11.16, 3.0.6, 3.1.6. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
How severe is CVE-2022-31000? CVE-2022-31000 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of solidus_backend are affected by CVE-2022-31000? solidus_backend (rubygems) versions < 2.11.16 is affected.
Is there a fix for CVE-2022-31000? Yes. CVE-2022-31000 is fixed in 2.11.16, 3.0.6, 3.1.6. Upgrade to this version or later.
Is CVE-2022-31000 exploitable, and should I be worried? Whether CVE-2022-31000 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-31000 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-31000?
- Upgrade solidus_backend to 2.11.16 or later
- Upgrade solidus_backend to 3.0.6 or later
- Upgrade solidus_backend to 3.1.6 or later