dbcve.org
Concrete CmsApplication · Concretecms

CVE-2026-8410

HIGH · 8.8 CVSS v3.1 Published 2026-05-21
Fix available
A fix is available. Upgrade to 9.5.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/dialog/logs/bulk/delete.  The The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.3 with vector 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. Thanks Yonatan Drori (Tenzai) for reporting.

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 · moderate confidence

Concrete CMS 9 before version 9.5.0 contains a Cross Site Request Forgery (CSRF) vulnerability at the bulk log deletion endpoint (concrete/controllers/dialog/logs/bulk/delete). An attacker could trick an authenticated administrator into unknowingly submitting a request to delete logs by embedding a malicious link or form on a third-party site.

MitigationUpgrade Concrete CMS to version 9.5.0 or later which includes CSRF protection at this endpoint. Alternatively, implement anti-CSRF token validation at the bulk delete logs controller before allowing deletion operations.

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
Concrete CmsApplication
Affected:>= 9.0.0, < 9.5.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Concrete CMS version
    Access the dashboard and navigate to Dashboard > System & Settings > Basics > Maintenance Mode, or check the composer.json file in the web root for the 'concrete/cms' package version
    Affected if Version is >= 9.0.0 and < 9.5.1
  2. Verify the logs dialog controller exists
    Check for the existence of the file /concrete/controllers/dialog/logs/bulk/delete.php or its routing configuration in the application
    Affected if The file exists and the version is in the affected range
  3. Confirm the bulk delete logs functionality is accessible
    Attempt to access the logs management interface at /ccm/system/dialogs/logs/bulk/delete or check routing configuration for this endpoint
    Affected if The endpoint is routable and the installed version is < 9.5.1

A user is affected if their Concrete CMS installation version is 9.0.0 through 9.5.0 (inclusive) and the logs bulk delete functionality is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.5.1 or later
Fixed in 9.5.1
Interim mitigation

Upgrade Concrete CMS to version 9.5.0 or later which includes CSRF protection at this endpoint. Alternatively, implement anti-CSRF token validation at the bulk delete logs controller before allowing deletion operations.

Recommended fix High confidence

Concrete CMS 9.5.1 or latest stable 9.x release

  1. 1. Back up your Concrete CMS database and files before performing any upgrade
  2. 2. Review the Concrete CMS 9.5.1 release notes for any important changes
  3. 3. Download Concrete CMS version 9.5.1 or the latest stable version from the official source (documentation.concretecms.org)
  4. 4. Upload the new files to your server, replacing the existing installation
  5. 5. Run the database upgrade process by accessing your site (the upgrade should auto-run)
  6. 6. Verify the CSRF protection is now in place by confirming the delete action at concrete/controllers/dialog/logs/bulk/delete requires proper tokens
  7. 7. Test that the logs bulk delete functionality works correctly after the upgrade
Caveat Minor releases in Concrete CMS typically include bug fixes and improvements; review the 9.5.1 changelog for any changes that may affect custom themes or add-ons

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Concrete Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8410 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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