dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8624

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LJ comments import: reloaded WordPress plugin (versions up to 0.97.1) contains a reflected XSS vulnerability via the PHP_SELF parameter. The PHP_SELF variable includes PATH_INFO that attackers can control, and the plugin echoes this value twice in the same function without sanitization or output escaping, allowing injection of arbitrary JavaScript through socially engineered links.

MitigationUpdate the plugin to the latest version and ensure all user-suprollable input (especially PHP_SELF/PATH_INFO) is sanitized via functions like sanitize_text_field() and properly escaped via esc_html() or esc_url() before output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if LJ comments import: reloaded plugin is installed
    Check your WordPress site's plugin directory or admin panel for the 'LJ comments import: reloaded' plugin. Also check for any plugin files with 'lj-comments' or similar naming in /wp-content/plugins/
    Affected if The plugin is installed and active on the WordPress site
  2. Locate PHP files that reference PHP_SELF
    Search the plugin directory for files containing 'PHP_SELF' - use grep or a file search tool to find: grep -r 'PHP_SELF' /path/to/wp-content/plugins/lj-comments-import-reloaded/
    Affected if Files containing PHP_SELF are found in the plugin directory
  3. Inspect echo points for unsanitized output
    Open each file containing PHP_SELF and examine code around echo or print statements that output this variable. Look for patterns like echo $_SERVER['PHP_SELF'] or similar without sanitization functions such as esc_url(), esc_attr(), or htmlspecialchars()
    Affected if Code outputs PHP_SELF without using WordPress sanitization functions like esc_url() or esc_attr() before echoing
  4. Verify the vulnerable function is reachable
    Check if the function containing the vulnerable echo points is callable via HTTP requests - examine if it handles incoming requests or is hooked to WordPress action/filter hooks that could be triggered via URL parameters
    Affected if The function with the vulnerable output can be reached via HTTP requests without authentication

If the LJ comments import: reloaded plugin is installed AND contains code that echoes PHP_SELF without sanitization via esc_url() or esc_attr(), the site is affected by this reflected XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version and ensure all user-suprollable input (especially PHP_SELF/PATH_INFO) is sanitized via functions like sanitize_text_field() and properly escaped via esc_html() or esc_url() before output.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8624 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data