Unauthorized calendar event creation via missing CSRF token
Published Sep 27, 2021 · Updated Aug 4, 2024
Cross-site request forgery in Concrete CMS 8.5.5 and earlier allows remote attackers to create calendar events through an authenticated user. The Calendar event-save endpoint accepts state-changing requests without verifying the ccm_token CSRF token. Exploitation requires an authenticated user with calendar-event access to submit an attacker-controlled request, allowing unauthorized event creation with that user’s permissions.
Summary
What happened
Cross-site request forgery in Concrete CMS 8.5.5 and earlier allows remote attackers to create calendar events through an authenticated user. The Calendar event-save endpoint accepts state-changing requests without verifying the ccm_token CSRF token. Exploitation requires an authenticated user with calendar-event access to submit an attacker-controlled request, allowing unauthorized event creation with that user’s permissions.
The record
- CVE
- CVE-2021-40108
- Published
- Sep 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo