{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92411 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92411 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92411 is a medium-severity cross-site scripting vulnerability in Unknown WP Delicious, published on 26 Sep 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-92411 and fix it if it is affected.\n\nWhat it is: CVE-2026-92411 is a medium-severity cross-site scripting vulnerability in Unknown WP Delicious, published on 26 Sep 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-92411 in the wild and no public exploit code.\n\nAffected product: Unknown WP Delicious. 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-92411/ (Markdown: https://insights.sbomify.com/CVE-2026-92411/index.md)","id":"CVE-2026-92411","markdown":"https://insights.sbomify.com/CVE-2026-92411/index.md","name":"CVE-2026-92411","record":{"aliases":["GHSA-9j5m-mgr6-gp3g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Contributors can inject arbitrary HTML and scripts into recipe pages via unescaped tag names, leading to stored XSS attacks on front-end viewers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WP Delicious  WordPress plugin before 1.10.8 does not validate or escape the HTML tag name taken from user-supplied recipe block data before rendering it on the front end, allowing users with the Contributor role and above to inject arbitrary HTML tags, including script tags, which execute when the recipe page is viewed.","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":"WP Delicious \u003c 1.10.8 - Contributor+ Stored XSS via Recipe Block Tag Name","id":"CVE-2026-92411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Five Star Restaurant Reviews \u003c 2.3.14 - Reflected XSS","id":"CVE-2026-92412"},"packages":[],"prev":{"headline":"Sign-up Sheets \u003c 2.4.0 - Arbitrary Sign-up Deletion via CSRF","id":"CVE-2026-92410"},"products":["WP Delicious"],"published":"2026-09-26","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":"total"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["Unknown"]},"summary":"Contributors can inject arbitrary HTML and scripts into recipe pages via unescaped tag names, leading to stored XSS attacks on front-end viewers.","url":"https://insights.sbomify.com/CVE-2026-92411/"}