WordPress plugin
LJ comments import: reloaded security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All LJ comments import: reloaded vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting via PHP_SELF Parameter ≤0.97.1No patch available | CVE-2026-8624 |
- Medium6.1Reflected Cross-Site Scripting via PHP_SELF Parameter
≤0.97.1No patch available
LJ comments import: reloaded: common questions
Does LJ comments import: reloaded have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in LJ comments import: reloaded: 1 medium. At least one is not fixed in the latest version.
How do I check which version of LJ comments import: reloaded I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent LJ comments import: reloaded vulnerability?
CVE-2026-8624, published May 19, 2026: LJ comments import: reloaded <= 0.97.1 - Reflected Cross-Site Scripting via PHP_SELF Parameter. Severity: Medium (CVSS 6.1).
Is any LJ comments import: reloaded vulnerability listed in CISA KEV?
No. None of the known LJ comments import: reloaded vulnerabilities is currently listed in the CISA KEV catalog.