EUVD-2026-78088
GHSA-xhpm-mjpp-w9gx
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable CSRF; no attacker privileges; UI:R because an authenticated editor must load the crafted request; I:H for permanent irreversible database-level content deletion; no confidentiality or availability impact.
Primary rating from Vendor (ConcreteCMS).
CVSS VectorVendor: ConcreteCMS
Lifecycle Timeline
2DescriptionCVE.org
Concrete CMS 9 through 9.5.2 did not validate a CSRF token in the orphaned block removal panel action (removeOrphanedBlocks). A remote attacker could craft a request that, when loaded by an authenticated user holding edit permission on the target page, deleted every block on that page's current version; blocks not aliased to another page or scrapbook entry were also removed from the global Blocks table and their block-type data table, permanently destroying the content. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 7.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N. Thanks Yonatan Drori from Tenzai for reporting.
AnalysisAI
Missing CSRF token validation on the orphaned block removal action (removeOrphanedBlocks) in Concrete CMS 9.0.0 through 9.5.2 enables remote attackers to permanently destroy all block content on any page the victim can edit. By tricking an authenticated editor into loading a crafted URL, an attacker triggers deletion of every block on the targeted page's current version; blocks not aliased elsewhere are additionally purged from the global Blocks table and their block-type data tables, making the destruction irreversible without a database backup. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Three concrete prerequisites must align: (1) the victim must hold edit permission on the specific Concrete CMS page being targeted - unprivileged site visitors cannot be used as attack proxies; (2) the victim must have an active authenticated session in the same browser that loads the attacker's crafted link, meaning they must be logged into the CMS admin panel at the time of exploitation; (3) the target site must run Concrete CMS 9.0.0 through 9.5.2 - no non-default configuration or optional feature flag is required since CSRF protection on this action was simply absent. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N) accurately captures the core trade-off: no attacker privileges and no special attack conditions are required, but exploitation is gated on one human interaction (UI:P), meaning an editor must visit a malicious link while authenticated. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to Concrete CMS 9.5.3 or later; the 9.5.3 release notes at https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes confirm the addition of CSRF token validation on the `removeOrphanedBlocks` endpoint. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all Concrete CMS instances running versions 9.0.0-9.5.2 and verify current database backups are restorable; immediately notify all users with editor roles to avoid clicking unfamiliar links and report suspicious emails. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Concrete Cms
View allA bypass of adding remote files in Concrete CMS (previously concrete5) File Manager leads to remote code execution in Co
Concrete5 through 8.5.5 deserializes Untrusted Data. Rated high severity (CVSS 7.2), this vulnerability is remotely expl
Concrete5 up to and including 8.5.2 allows Unrestricted Upload of File with Dangerous Type such as a .php file via File
Concrete5 before 8.5.3 allows Unrestricted Upload of File with Dangerous Type such as a .phar file. Rated high severity
A Server Side Request Forgery (SSRF) vulnerability in tools/files/importers/remote.php in concrete5 8.2.0 can lead to at
Unauthenticated file usage disclosure in Concrete CMS 9.5.0 and below exposes internal page structure to any network-acc
concrete5 8.1.0 places incorrect trust in the HTTP Host header during caching, if the administrator did not define a "ca
Concrete CMS versions below 9.4.8 contain a cross-site request forgery vulnerability in the Anti-Spam Allowlist Group Co
concrete5 8.1.0 has CSRF in Thumbnail Editor in the File Manager, which allows remote attackers to disable the entire in
Unauthenticated information disclosure in Concrete CMS 9.5.0 and earlier allows remote attackers to enumerate all conver
Unauthenticated information disclosure in Concrete CMS 9.5.0 and below allows any network-accessible attacker to enumera
Concrete CMS before 8.5.13 and 9.x before 9.2.2 allows unauthorized access because directories can be created with insec
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today