Skip to main content
VulnerabilityPublished Updated

CVE-2024-24131: SuperWebMailer · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% 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 7 Feb 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

  4. 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
GitHubhebing123/SuperWebMailerpkg:github/hebing123/SuperWebMailerOther threatsAffected
  • =9.31.0.01799
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. Immediate mitigation should include input validation and output encoding on all parameters handled by api.php to prevent injection of malicious scripts.
  2. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers.
  3. Educate users and administrators about the risks of clicking on suspicious links, especially those related to email marketing platforms.
  4. Monitor web server logs and application logs for unusual request patterns targeting api.php or containing suspicious payloads.
  5. If possible, restrict access to the api.php endpoint to trusted IP addresses or authenticated users only, reducing exposure.
  6. Apply any vendor-released patches or updates as soon as they become available.
  7. Conduct regular security assessments and penetration testing focusing on web application vulnerabilities, including XSS.
  8. Use web application firewalls (WAFs) with rules designed to detect and block reflected XSS attempts targeting the application.
  9. Review and harden session management to limit the impact of stolen session tokens, including setting secure, HttpOnly cookies and short session lifetimes.

Description

SuperWebMailer v9.31.0.01799 was discovered to contain a reflected cross-site scripting (XSS) vulenrability via the component api.php.

References

Community reviews

Loading reviews…