CVE-2026-81907
Last modified
CVE-2026-81907 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Concrete CMS | Concrete CMS | >= 5.0.0, <= 9.5.2 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-81907?
How severe is CVE-2026-81907?
How do I fix CVE-2026-81907?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81901In Concrete CMS 9.2.0 through 9.5.2, the REST API page updat…8.7
- CVE-2026-81902Concrete CMS 9 through 9.5.2 did not validate a CSRF token i…8.1
- CVE-2026-81903Concrete CMS versions 9.0.0 to 9.5.2 stored the Page Contain…5.4
- CVE-2026-81904Concrete CMS below 9.5.3 registered view assets for every su…6.3
- CVE-2026-81905Concrete CMS below 9.5.3 stores user validation hashes for m…6.3
- CVE-2026-81906Concrete CMS OAuth callback login path prior to version 9.5.…6.3
- CVE-2026-81908Concrete CMS 9.2.0 to 9.5.2 contain a missing authorization …6
- CVE-2026-81909Concrete CMS 9 through 9.5.2 is vulnerable to Missing Author…5.9
- CVE-2026-8191A vulnerability was identified in Wavlink NU516U1 M16U1_V240…8.8
- CVE-2026-81910Concrete CMS 9 through 9.5.2 is vulnerable to Server-Side Te…6.5
- CVE-2026-81911Concrete CMS versions 9.0.0 to 9.5.2 is vulnerable to Stored…5.4
- CVE-2026-81912Concrete CMS before 9.5.3 is vulnerable to Cross-Site Reques…5.7
Are you affected by CVE-2026-81907?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
