Concrete CMS vulnerable to Cross-Site Request Forgery (CSRF)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-2994: 0.24% estimated exploitation activity in the next 30 days; percentile 14.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Concrete CMS below version 9.4.8 is subject to CSRF by a Rogue Administrator using the Anti-Spam Allowlist Group Configuration via groupid parameter which can leads to a security bypass since changes are saved prior to checking the CSRF token. The Concrete CMS security team thanks z3rco for reporting

Published by the source

4 Mar 2026, 03:31 UTC

Last modified by the source

4 Mar 2026, 21:35 UTC

Source last checked

26 Oct 2026, 14:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6mxw-2vhf-42g5

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

# Patch Next advisory brief: CVE-2026-2994

Advisory: Concrete CMS vulnerable to Cross-Site Request Forgery (CSRF)
IDs: CVE-2026-2994, GHSA-6mxw-2vhf-42g5
Record: https://patchnext.com/advisories/cve-2026-2994 (revision 1, source checked 26 Oct 2026, 14:38 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: concrete5/concrete5 9.4.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist concrete5/concrete5: affected < 9.4.8; fixed in 9.4.8

## Suggested inspection (read-only)
- Packagist concrete5/concrete5: 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 concrete5/concrete5.
- 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-6mxw-2vhf-42g5 (GitHub-reviewed advisory GHSA-6mxw-2vhf-42g5 lists affected ranges: Packagist concrete5/concrete5 >=0 <9.4.8)

Commands are suggestions: review each one before running it.