{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66706 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66706 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66706 is a medium-severity cross-site scripting vulnerability in Mark Jaquith Subscribe to Comments, published on 6 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-66706 and fix it if it is affected.\n\nWhat it is: CVE-2026-66706 is a medium-severity cross-site scripting vulnerability in Mark Jaquith Subscribe to Comments, published on 6 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-66706 in the wild and no public exploit code.\n\nAffected product: Mark Jaquith Subscribe to Comments. 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-66706/ (Markdown: https://insights.sbomify.com/CVE-2026-66706/index.md)","id":"CVE-2026-66706","markdown":"https://insights.sbomify.com/CVE-2026-66706/index.md","name":"CVE-2026-66706","record":{"aliases":["GHSA-2j9x-ww5c-7853"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"An attacker can inject malicious scripts via the Subscribe to Comments plugin, potentially compromising user sessions or executing code in the browser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Author Cross Site Scripting (XSS) in Subscribe to Comments \u003c= 2.3.1 versions.","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":"WordPress Subscribe to Comments plugin \u003c= 2.3.1 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2026-66706","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Facebook for WooCommerce plugin \u003c= 3.7.5 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2026-66707"},"packages":[],"prev":{"headline":"WordPress Facebook for WordPress plugin \u003c= 5.2.1 - Cross Site Scripting (XSS) vulnerability","id":"CVE-2026-66705"},"products":["Subscribe to Comments"],"published":"2026-08-06","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-08-06","vendors":["Mark Jaquith"]},"summary":"An attacker can inject malicious scripts via the Subscribe to Comments plugin, potentially compromising user sessions or executing code in the browser.","url":"https://insights.sbomify.com/CVE-2026-66706/"}