How severe is GHSA-8639-qx56-r428?

GHSA-8639-qx56-r428 has a CVSS score of 2.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8639-qx56-r428?

GHSA-8639-qx56-r428 affects the following packages: solidus_backend (RubyGems), solidus_backend (RubyGems), solidus_backend (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-8639-qx56-r428?

Update solidus_backend to 2.11.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8639-qx56-r428 is resolved across your whole dependency graph.

How do I detect GHSA-8639-qx56-r428 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solidus_backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8639-qx56-r428 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8639-qx56-r428?

O3 pinpoints whether GHSA-8639-qx56-r428 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8639-qx56-r428 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-8639-qx56-r428, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-8639-qx56-r428?

GHSA-8639-qx56-r428 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8639-qx56-r428?

GHSA-8639-qx56-r428 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8639-qx56-r428 published, and has it been updated?

GHSA-8639-qx56-r428 was published on June 1, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

GHSA-8639-qx56-r428

LOW

CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend

Also known asCVE-2022-31000

Published

Jun 1, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk28th percentile+0.21%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

💎solidus_backend💎solidus_backend💎solidus_backend

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

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.

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`solidus_backend`	all versions	2.11.16
💎RubyGems	`solidus_backend`	≥ 3.0.0&&< 3.0.6	3.0.6
💎RubyGems	`solidus_backend`	≥ 3.1.0&&< 3.1.6	3.1.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

solidus_backend is the admin interface for the Solidus e-commerce framew…

github.comNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solidus_backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update solidus_backend to 2.11.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8639-qx56-r428 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8639-qx56-r428 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8639-qx56-r428. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-8639-qx56-r428 in your dependencies?

O3 detects GHSA-8639-qx56-r428 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works