LiveActive security incident?Get immediate response
CVE Record

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

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.

LowCVSS 2.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity CSRF issue in the Solidus e-commerce admin interface. In affected versions, an attacker who knows an order number could cause an administrator’s browser to finalize or unfinalize that order’s adjustments. The business impact is limited to order-adjustment integrity, but stores using affected Solidus Backend versions should patch.

Executive priority

Handle through normal patch management unless the Solidus admin interface is broadly exposed or order-adjustment integrity is business-critical. The vulnerability is low severity, but the fix is clear and vendor-provided.

Technical view

CVE-2022-31000 is CWE-352 in solidus_backend before 3.1.6, 3.0.6, and 2.11.16. It allows changing the state of an order’s adjustments when the attacker has the order number and execution occurs on a store administrator’s computer. CVSS is 2.3, integrity impact low.

Likely exposure

Exposure is limited to Solidus stores running vulnerable solidus_backend versions: below 2.11.16, 3.0.0 to below 3.0.6, or 3.1.0 to below 3.1.6. Risk is higher where administrators stay logged in and the admin interface is reachable.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described attack requires an affected Solidus Backend deployment, knowledge of an order number, and execution in the context of a store administrator’s computer.

Researcher notes

Keep scope narrow: sources support CSRF affecting order adjustment finalize/unfinalize state only. They do not establish broader order modification, data exposure, availability impact, or active exploitation. Use the vendor advisory and patch commit as primary references.

Mitigation direction

  • Upgrade solidus_backend to 3.1.6, 3.0.6, or 2.11.16 as applicable.
  • Restrict access to the Solidus admin interface to trusted networks or authenticated paths.
  • Review vendor guidance before applying any workaround not named in the advisory.
  • Monitor order adjustment state changes for unexpected finalize or unfinalize activity.

Validation and detection

  • Check dependency manifests for the installed solidus_backend version.
  • Confirm production and staging stores are not on affected version ranges.
  • Review admin access paths and session exposure for Solidus Backend.
  • Audit recent order adjustment state changes for unexplained activity.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-31000 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N0.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.3Low
CVSS 3.1 vector shape for CVE-2022-31000Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
solidusiosolidus< 2.11.16, >= 3.0.0, < 3.0.6, >= 3.1.0, < 3.1.6Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.