CVE-2021-22954
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA cross-site request forgery vulnerability exists in Concrete CMS <v9 that could allow an attacker to make requests on behalf of other users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA cross-site request forgery (CSRF) vulnerability in Concrete CMS versions prior to v9 allows remote attackers to trick authenticated users into unknowingly executing unwanted actions on the CMS, such as modifying content or settings, by embedding malicious requests into links or pages the user visits.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Concrete CMS versionLog into the CMS admin dashboard and navigate to the Dashboard > About page, or check the version file in the concrete directory if you have filesystem accessAffected if The version displayed is any version prior to 9.0 (e.g., 8.5.x, 8.4.x, etc.)
-
Locate the CSRF configuration settingsAccess the concrete/config directory and inspect the CSRF protection configuration files, typically named csrf.php or within the app configurationAffected if CSRF token validation is disabled, missing, or improperly configured in the configuration files
-
Verify CSRF token validation on form submissionsSubmit a state-changing request (such as saving a page or modifying settings) without including a valid CSRF token in the request and observe whether the action is executedAffected if The action completes successfully without requiring a valid CSRF token, indicating token validation is not enforced
-
Check the core CSRF token implementationExamine the concrete/src/Validation/CSRF directory for the token validation logic, if you have code accessAffected if The token validation functions are missing, incomplete, or do not verify both the token and the request origin
Your environment is affected if the installed Concrete CMS version is below 9.0 and CSRF token validation is either disabled, missing, or not properly enforced on authenticated requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.0
Upgrade Concrete CMS to version 9 or later to incorporate proper CSRF token validation and request origin verification.
Concrete CMS 9.0 or later
- Download Concrete CMS version 9.0 or later from the official source (documentation.concretecms.org/display/AD10/Download+Concrete+CMS)
- Backup your current database and files before upgrading
- Follow the official upgrade instructions for Concrete CMS 9.0
- Test the upgrade in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22954 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22954 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data