CVE-2024-56116: Amiro.CMS · A Cross-Site Request Forgery
Affects Amiro.CMSSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 7.8.4 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.8.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade compliancecontrol/Amiro.CMS to 7.8.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubcompliancecontrol/Amiro.CMSpkg:github/compliancecontrol/Amiro.CMSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately upgrade Amiro.CMS installations to version 7.8.4 or later once available, as this version addresses the CSRF vulnerability.
- Implement web application firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting Amiro.CMS endpoints.
- Enforce strict Content Security Policy (CSP) headers to reduce the risk of malicious cross-site requests.
- Educate users, especially administrators, about the risks of clicking on untrusted links or visiting suspicious websites to mitigate social engineering vectors.
- Monitor web server and application logs for unusual account creation activities or anomalous administrative actions.
- Employ multi-factor authentication (MFA) for administrative accounts to add an additional layer of security even if account creation is compromised.
- Disable or restrict administrative account creation features via the CMS configuration if not required.
- Conduct regular security assessments and penetration testing focused on CSRF and privilege escalation vectors.
- Prepare incident response plans specifically addressing CMS compromise scenarios to enable rapid containment and recovery.
Description
A Cross-Site Request Forgery vulnerability in Amiro.CMS before 7.8.4 allows remote attackers to create an administrator account.