{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-18978 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18978 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18978 is a high-severity cross-site scripting vulnerability in litespeedtech LiteSpeed Cache, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18978 and fix it if it is affected.\n\nWhat it is: CVE-2026-18978 is a high-severity cross-site scripting vulnerability in litespeedtech LiteSpeed Cache, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18978 in the wild and no public exploit code.\n\nAffected product: litespeedtech LiteSpeed Cache. 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-18978/ (Markdown: https://insights.sbomify.com/CVE-2026-18978/index.md)","id":"CVE-2026-18978","markdown":"https://insights.sbomify.com/CVE-2026-18978/index.md","name":"CVE-2026-18978","record":{"aliases":["GHSA-rm48-v2jm-fxxq"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via comments in LiteSpeed Cache, potentially leading to code execution or account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 7.8.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A comment payload crafted exclusively from decimal numeric character references (e.g. \u0026#34;, \u0026#60;, \u0026#62;) placed inside an allowed element such as \u0026lt;code\u0026gt; bypasses WordPress's wp_kses sanitization, as kses does not treat a data-settings=\"...\" substring within text content as an HTML attribute, allowing the malicious payload to reach the vulnerable function. For this to be exploitable, the site must allow users with previously approved comments to write new comments, and the require_name_email setting must be disabled.","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":"LiteSpeed Cache \u003c= 7.8.1 - Unauthenticated Stored Cross-Site Scripting via Comment Content","id":"CVE-2026-18978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"nearai ironclaw shell.rs classify_command_risk command injection","id":"CVE-2026-18980"},"packages":[],"prev":{"headline":"NousResearch hermes-agent disabled_toolsets agent_init.py get_tool_definitions privileges assignment","id":"CVE-2026-18976"},"products":["LiteSpeed Cache"],"published":"2026-08-28","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["litespeedtech"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via comments in LiteSpeed Cache, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2026-18978/"}