Skip to main content
CVE-2024-56115VulnerabilityPublished Updated

CVE-2024-56115: Amiro.CMS · n/a

Affects Amiro.CMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium : upgrade to 7.8.4 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% 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:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Upgrade compliancecontrol/Amiro.CMS to 7.8.4.

Affected software

ProductAffectedFixed in
GitHubcompliancecontrol/Amiro.CMSpkg:github/compliancecontrol/Amiro.CMSOther threatsAffected
  • <7.8.4
Fixed in
  • 7.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-56115, organizations should immediately upgrade Amiro.CMS to version 7.8.4 or later once available, as this version addresses the vulnerability by properly neutralizing special elements in user input. If you cannot patch yet, administrators should implement strict input validation and output encoding on all user-supplied data to prevent script injection. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. Web Application Firewalls (WAFs) configured to detect and block XSS payloads can provide an additional layer of defense. Regular security audits and penetration testing focused on input handling can identify residual vulnerabilities. User education to recognize phishing attempts and suspicious links is also critical since exploitation requires user interaction. Monitoring web server logs for unusual requests and anomalous behavior can aid in early detection of exploitation attempts. Finally, organizations should maintain an incident response plan tailored to web application attacks to respond swiftly if exploitation occurs.

Description

A vulnerability in Amiro.CMS before 7.8.4 exists due to the failure to take measures to neutralize special elements. It allows remote attackers to conduct a Cross-Site Scripting (XSS) attack.

References

Community reviews

Loading reviews…