CVE-2026-81909 Concrete CMS CVE debrief

Who should care

Defenders of Concrete CMS installations, particularly those with user-delegated area-scoped add_block_to_area permissions, should assess exposure and verify block alias route authorization.

Why it matters

This Missing Authorization vulnerability in Concrete CMS 9-9.5.2 allows an attacker to disclose and delete arbitrary block content, potentially disrupting site functionality. Defenders should prioritize verifying block alias route authorization, restricting access, and monitoring for suspicious activities.

• Content disclosure: an attacker can access the content of arbitrary blocks
• Content destruction: an attacker can delete arbitrary blocks, potentially disrupting site functionality
• Privilege escalation: an attacker with limited permissions can manipulate block content and structure
• Verification priority: defenders need to verify block alias route authorization and monitor for suspicious activities

Technical summary

The block alias route in Concrete CMS 9 through 9.5.2 does not verify that the referenced block is genuinely orphaned on the target page, nor that the caller holds any permission over the source block. This allows a user with area-scoped add_block_to_area delegation on their own page to pass any block ID on the site, duplicating the source block's content into an area they control and force-deleting the original block.

Defensive priority

Defenders should prioritize verifying and restricting block alias route access, ensuring proper authorization for block modifications, and monitoring for suspicious block duplication and deletion activities.

Recommended defensive actions

• Verify and restrict access to the block alias route
• Ensure proper authorization for block modifications
• Monitor for suspicious block duplication and deletion activities
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was reported by Yonatan Drori from Tenzai. The Concrete CMS security team assigned a CVSS v4.0 score of 5.9. Evidence is limited to the report and the CVSS score. Defenders should verify block alias route authorization and monitor for suspicious block duplication and deletion activities. The CVE record was published on 2026-09-11T18:16:58.930Z.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.