Cross-Site Request Forgery (CSRF) in Concrete CMS (CVE-2026-81907)
Summary
Vulnerability in Concrete CMS (CVE-2026-81907). Data can be tampered with by attackers. Exploitable via POST /index.php/dashboard/system/express/entities/delete_entries.
Original description
The description as published by the source.
Concrete CMS 9.5.2 and below is vulnerable to Cross-Site Request Forgery (CSRF) in the Express "Clear Entries" function (POST /index.php/dashboard/system/express/entities/delete_entries) because the controller records but does not enforce a failed CSRF token check, allowing the destructive operation to proceed when the token is missing or invalid. A remote unauthenticated attacker can force an authenticated administrator who visits an attacker-controlled page to permanently delete all entries belonging to an attacker-selected Express entity on a web application to which the administrator is currently authenticated. Because the default Contact Express object ships with a fixed entity UUID, the target identifier can be obtained without dashboard access. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 6.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N. Thanks Pratik Zanjurne for reporting.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-81907 has been found in Concrete CMS.
Attackers can target a specific entry point like POST /index.php/dashboard/system/express/entities/delete_entries over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Concrete CMS CVE-2026-81907" on the vendor's site.
CVE-2026-81907 (Concrete CMS) — CWE-352 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: POST /index.php/dashboard/system/express/entities/delete_entries
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in Concrete CMS. Attackers reach the vulnerable code path via POST /index.php/dashboard/system/express/entities/delete_entries without authentication.
Check the vendor advisory for the affected versions of Concrete CMS. Attack surface: POST /index.php/dashboard/system/express/entities/delete_entries.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /index.php/dashboard/system/express/entities/delete_entries requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Concrete CMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /index.php/dashboard/system/express/entities/delete_entries' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /index.php/dashboard/system/express/entities/delete_entriesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /index.php/dashboard/system/express/entities/delete_entries on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web documentation.concretecms.org
- web nvd.nist.gov
- web github.com