Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3

Authentication Bypass by CSRF Weakness

GHSA-5629-8855-gf4g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (solidus_core 3.1.3, 3.0.3, 2.11.12), 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_core

    Affected
    < 2.11.12>= 3.0.0, < 3.0.3>= 3.1.0, < 3.1.3
    Fixed in
    3.1.3, 3.0.3, 2.11.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact The actual vulnerability has been discovered on solidusauthdevise. See GHSA-xm34-v85h-9pg2 for details. The security advisory here exists to provide an extra layer of security in the form of a monkey patch for users who don't update solidusauthdevise. For this reason, it has been marked as low impact on this end. Patches For extra security, update soliduscore to versions 3.1.3, 3.0.3 or 2.11.12. Workarounds Look at the workarounds described at GHSA-xm34-v85h-9pg2. References - GHSA-xm34-v85h-9pg2. For more information If you have any questions or comments about this advisory: Open an issue in solidusauthdevise or a discussion in solidus Email us at security@solidus.io Contact the core team on Slack

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

    Published from ghsa record GHSA-5629-8855-gf4g

Agent brief

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

# Patch Next advisory brief: GHSA-5629-8855-gf4g

Advisory: Authentication Bypass by CSRF Weakness
IDs: GHSA-5629-8855-gf4g
Record: https://patchnext.com/advisories/ghsa-5629-8855-gf4g (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: solidus_core 3.1.3, 3.0.3, 2.11.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- RubyGems solidus_core: affected < 2.11.12; >= 3.0.0, < 3.0.3; >= 3.1.0, < 3.1.3; fixed in 3.1.3, 3.0.3, 2.11.12

## Suggested inspection (read-only)
- RubyGems solidus_core: 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_core.
- 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-5629-8855-gf4g (GitHub-reviewed advisory GHSA-5629-8855-gf4g lists affected ranges: RubyGems solidus_core >=0 =3.0.0 =3.1.0 <3.1.3)

Commands are suggestions: review each one before running it.

Loading voting…