{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-1866 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1866 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1866 is a high-severity cross-site scripting vulnerability in jeroenpeters1986 Name Directory, published on 10 Feb 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-1866 and fix it if it is affected.\n\nWhat it is: CVE-2026-1866 is a high-severity cross-site scripting vulnerability in jeroenpeters1986 Name Directory, published on 10 Feb 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-1866 in the wild and no public exploit code.\n\nAffected product: jeroenpeters1986 Name Directory. 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-1866/ (Markdown: https://insights.sbomify.com/CVE-2026-1866/index.md)","id":"CVE-2026-1866","markdown":"https://insights.sbomify.com/CVE-2026-1866/index.md","name":"CVE-2026-1866","record":{"aliases":["GHSA-wj7p-g9vc-3935"],"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 scripts via double HTML-entity encoding in the Name Directory plugin submission form, leading to stored XSS.","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 Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin's sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the 'name_directory_name' and 'name_directory_description' parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.","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":"Cross-site scripting in Name Directory","id":"CVE-2026-1866","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"WP Front User Submit \u003c 5.0.6 - Unauthenticated Sensitive Information Exposure","id":"CVE-2026-1867"},"packages":[],"prev":{"headline":"User Registration \u0026 Membership \u003c= 5.1.2 - Authenticated (Subscriber+) SQL Injection via membership_ids[]","id":"CVE-2026-1865"},"products":["Name Directory"],"published":"2026-02-10","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-04-08","vendors":["jeroenpeters1986"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via double HTML-entity encoding in the Name Directory plugin submission form, leading to stored XSS.","url":"https://insights.sbomify.com/CVE-2026-1866/"}