Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3

CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend

CVE-2022-31000GHSA-8639-qx56-r428

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (solidus_backend 3.1.6, 3.0.6, 2.11.16), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • RubyGems solidus_backend

    Affected
    < 2.11.16>= 3.0.0, < 3.0.6>= 3.1.0, < 3.1.6
    Fixed in
    2.11.16, 3.0.6, 3.1.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.3 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2022-31000: 0.41% estimated exploitation activity in the next 30 days; percentile 35.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 {yoursiteurl}/admin/orders/{ordernumber}/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 {yoursiteurl}/admin/orders/{ordernumber}/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 solidusbackend v3.1.6, v3.0.6, or v2.11.16, depending on the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8639-qx56-r428

Agent brief

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

# Patch Next advisory brief: CVE-2022-31000

Advisory: CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend
IDs: CVE-2022-31000, GHSA-8639-qx56-r428
Record: https://patchnext.com/advisories/cve-2022-31000 (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: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: solidus_backend 3.1.6, 3.0.6, 2.11.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems solidus_backend: affected < 2.11.16; >= 3.0.0, < 3.0.6; >= 3.1.0, < 3.1.6; fixed in 2.11.16, 3.0.6, 3.1.6

## Suggested inspection (read-only)
- RubyGems solidus_backend: 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_backend.
- 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-8639-qx56-r428 (GitHub-reviewed advisory GHSA-8639-qx56-r428 lists affected ranges: RubyGems solidus_backend >=0 =3.0.0 =3.1.0 <3.1.6)

Commands are suggestions: review each one before running it.

Loading voting…