Skip to main content
VulnerabilityPublished

CVE-2024-42749: altocms · Cross-site Scripting

Affects altocmsSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 14 Nov 2025

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubaltocms/altocmspkg:github/altocms/altocmsOther threatsAffected
  • =1.1.13
Fixed in–

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

AI-suggested

1. Implement strict input validation and output encoding on all user-supplied data within Alto CMS to prevent injection of malicious scripts. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3. Educate users and administrators to recognize and avoid interacting with suspicious links or content that could trigger the XSS exploit. 4. Monitor web traffic and logs for unusual activity indicative of attempted XSS exploitation. 5. If possible, isolate Alto CMS instances behind web application firewalls (WAFs) configured to detect and block XSS payloads. 6. Regularly review and update CMS components and plugins to minimize attack surface. 7. Engage with Alto CMS developers or community to track patch releases and apply updates promptly once available. 8. Consider temporary disabling or restricting features that accept user input until a patch is released. 9. Conduct security testing and code review focused on input handling to identify and remediate similar vulnerabilities proactively.

Description

Cross Site Scripting vulnerability in Alto CMS v.1.1.13 allows a local attacker to execute arbitrary code via a crafted script.

References

Community reviews

Loading reviews…