CVE-2026-8624: LJ comments import: reloaded (WordPress plugin) · Cross-site Scripting
Affects LJ comments import: reloaded (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% 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 20 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| etspringLJ comments import: reloaded | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory channels for updates. As a temporary measure, administrators may consider disabling or removing the vulnerable plugin until a fix is released. Additionally, applying web application firewall (WAF) rules to detect and block suspicious requests targeting PHP_SELF parameters may help mitigate risk.
Description
The LJ comments import: reloaded plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Parameter in all versions up to, and including, 0.97.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The vulnerability arises specifically because PHP_SELF includes attacker-controllable PATH_INFO appended to the script name, and there are two distinct unsanitized echo points for this value in the same function.
References
- wordfence.com/threat-intel/vulnerabilities/id/0f09cb59-dbbb-48a3-aeac-377f6ec87b88?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/lj-comments-import-reloaded/trunk/lj_comments_import.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/lj-comments-import-reloaded/trunk/lj_comments_import.php (opens in a new tab)