{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6404 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6404 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6404 is a medium-severity cross-site scripting vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6404 and fix it if it is affected.\n\nWhat it is: CVE-2026-6404 is a medium-severity cross-site scripting vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6404 in the wild and no public exploit code.\n\nAffected product: simonholliday Anomify AI – Anomaly Detection and Alerting. 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-6404/ (Markdown: https://insights.sbomify.com/CVE-2026-6404/index.md)","id":"CVE-2026-6404","markdown":"https://insights.sbomify.com/CVE-2026-6404/index.md","name":"CVE-2026-6404","record":{"aliases":["GHSA-58gg-mqhx-3cgq"],"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":"Authenticated administrators can inject arbitrary scripts via the API key parameter, leading to stored XSS execution on the settings page.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/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 Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'anomify_api_key' parameter in versions up to and including 0.3.6. This is due to insufficient input sanitization and missing output escaping: the plugin applies sanitize_text_field() to the Metric Data Key input before saving it via update_option(), but sanitize_text_field() strips HTML tags without encoding double-quote characters, and the value is then echoed directly into an HTML attribute context (value=\"...\") without esc_attr(). This makes it possible for authenticated attackers with administrator-level access to inject arbitrary web scripts that execute whenever a user visits the plugin's settings page.","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":"Anomify AI \u003c= 0.3.6 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'anomify_api_key' Parameter","id":"CVE-2026-6404","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Anomify AI \u003c= 0.3.6 - Cross-Site Request Forgery","id":"CVE-2026-6405"},"packages":[],"prev":{"headline":"Quick Playground \u003c= 1.3.3 - Unauthenticated Path Traversal to Arbitrary File Read via 'stylesheet' Parameter","id":"CVE-2026-6403"},"products":["Anomify AI – Anomaly Detection and Alerting"],"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":["simonholliday"]},"summary":"Authenticated administrators can inject arbitrary scripts via the API key parameter, leading to stored XSS execution on the settings page.","url":"https://insights.sbomify.com/CVE-2026-6404/"}