{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8624 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8624 is a medium-severity cross-site scripting vulnerability in etspring LJ comments import: reloaded, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-8624 and fix it if it is affected.\n\nWhat it is: CVE-2026-8624 is a medium-severity cross-site scripting vulnerability in etspring LJ comments import: reloaded, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-8624 in the wild and no public exploit code.\n\nAffected product: etspring LJ comments import: reloaded. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8624/ (Markdown: https://insights.sbomify.com/CVE-2026-8624/index.md)","id":"CVE-2026-8624","markdown":"https://insights.sbomify.com/CVE-2026-8624/index.md","name":"CVE-2026-8624","record":{"aliases":["GHSA-r7gc-qvc7-g642"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary web scripts via the PHP_SELF parameter in the LJ comments import: reloaded WordPress plugin, requiring user interaction to execute.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"LJ comments import: reloaded \u003c= 0.97.1 - Reflected Cross-Site Scripting via PHP_SELF Parameter","id":"CVE-2026-8624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Dear Flipbook \u003c= 2.4.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via '.df-element' Element Inner HTML","id":"CVE-2026-8625"},"packages":[],"prev":{"headline":"Dear Flipbook \u003c= 2.4.30 - Authenticated (Contributor+) Stored Cross-Site Scripting via '.dvcss' Element Class Attribute","id":"CVE-2026-8623"},"products":["LJ comments import: reloaded"],"published":"2026-05-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["etspring"]},"summary":"Unauthenticated attackers can inject arbitrary web scripts via the PHP_SELF parameter in the LJ comments import: reloaded WordPress plugin, requiring user interaction to execute.","url":"https://insights.sbomify.com/CVE-2026-8624/"}