Concrete CMS before 9.5.3 is vulnerable to Cross-Site Request Forgery (CSRF) in the theme page-template activation feature. The Dashboard theme Inspect controller's activate_files() action created PageTemplate records from attacker-supplied pageTemplates[] values without validating an anti-CSRF token.A remote attacker could host a page that auto-submitted a forged POST request; when a signed-in administrator visited it, the request executed under the administrator's session and created theme page-template records, changing site configuration without the administrator's consent. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Andrew Gonzalez for reporting.
CVE-2026-81924
Score 6.5 from GitHub Security Advisory (severity: LOW) published 2026-09-15. NVD baseline CVSS 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 21, 2026
References (1)
- ff5b8ace-8b95-4078-9743-eac1ca5451dehttps://documentation.concretecms.org/developers/introduction/version-history/953-release-notes
Vendor Advisories for CVE-2026-81924(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 19:52 UTCEG score recompute
- 2026-09-24 19:52 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 19:20 UTCEG score recompute
- 2026-09-23 19:20 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 18:27 UTCEG score recompute
- 2026-09-22 18:27 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 17:55 UTCEG score recompute▲ 4.40
- 2026-09-21 17:55 UTCGHSA enrichment
- 2026-09-21 17:55 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 22:52 UTCEG score recompute
- 2026-09-19 22:52 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-16 19:23 UTCEG score recompute
- 2026-09-16 19:23 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 20:41 UTCEG score recompute
- 2026-09-15 19:32 UTCEG score recompute
- 2026-09-15 19:03 UTCEG score recompute
- 2026-09-15 19:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81924?
When was CVE-2026-81924 disclosed?
Is CVE-2026-81924 actively exploited?
What is the CVSS score of CVE-2026-81924?
How do I remediate CVE-2026-81924?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81924
Is Your Infrastructure Affected by CVE-2026-81924?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.