CVE-2024-22551: WhatACart · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Jan 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubWhatACartpkg:github/WhatACartOther 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
To mitigate this vulnerability, organizations using WhatACart v2.0.7 should implement strict input validation and output encoding on the /site/default/search component to neutralize any malicious scripts. Employing Content Security Policy (CSP) headers can reduce the impact of XSS by restricting the sources from which scripts can be loaded. Web Application Firewalls (WAFs) configured to detect and block reflected XSS payloads can provide an additional layer of defense. User education to recognize phishing attempts and suspicious URLs is also critical. Regular security assessments and penetration testing focused on XSS vulnerabilities should be conducted to identify and remediate similar issues proactively.
Description
WhatACart v2.0.7 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the component /site/default/search.