CVE-2024-13352: Legull (WordPress plugin) · Cross-Site Scripting (XSS)
Affects Legull (WordPress plugin)Source CVE Database V5
Not known to be exploited · public detection template (Nuclei) · CVSS 7.1 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Feb 2025
Detectable: evidence found.
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Legull | Affected
| Fixed in– |
AI-suggested
1. Monitor for and apply official patches or updates from the Legull plugin developers as soon as they become available. 2. In the absence of patches, implement Web Application Firewalls (WAFs) with specific rules to detect and block reflected XSS payloads targeting the vulnerable parameter. 3. Restrict administrative access to the WordPress backend by IP whitelisting or VPN-only access to reduce exposure to phishing attempts. 4. Educate administrators and high-privilege users about the risks of clicking untrusted links, especially those that could trigger reflected XSS attacks. 5. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on the site. 6. Regularly audit plugin usage and remove unnecessary or outdated plugins to reduce attack surface. 7. Use security plugins that can detect and alert on suspicious activities related to XSS attempts.
Description
The Legull WordPress plugin through 1.2.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.