{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6405 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6405 is a medium-severity vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-6405 and fix it if it is affected.\n\nWhat it is: CVE-2026-6405 is a medium-severity vulnerability in simonholliday Anomify AI – Anomaly Detection and Alerting, published on 20 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-6405 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-6405/ (Markdown: https://insights.sbomify.com/CVE-2026-6405/index.md)","id":"CVE-2026-6405","markdown":"https://insights.sbomify.com/CVE-2026-6405/index.md","name":"CVE-2026-6405","record":{"aliases":["GHSA-6hfc-j326-f823"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick admins into submitting forged requests to inject malicious scripts, leading to code execution and privilege escalation in the Anomify AI plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Anomify AI – Anomaly Detection and Alerting plugin for WordPress is vulnerable to Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS) in versions up to and including 0.3.6. This is due to missing nonce verification on the settings page handler and insufficient output escaping in the admin_options.php template. The settings form includes no wp_nonce_field() and the handler performs no check_admin_referer() check, meaning any cross-origin POST can modify plugin settings. The API key field is sanitized only with sanitize_text_field(), which strips HTML tags but does not encode double-quote characters; the value is then rendered into an HTML attribute via bare echo without esc_attr(), allowing a double-quote attribute-escape payload to survive both sanitization and storage. This makes it possible for unauthenticated attackers to inject arbitrary web scripts by tricking a logged-in administrator into visiting a malicious page that submits a forged request, storing the payload in the database and causing it to execute in the administrator's browser whenever the plugin settings page is visited.","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 - Cross-Site Request Forgery","id":"CVE-2026-6405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Docker Desktop Enhanced Container Isolation bypass via --use-api-socket CLI flag","id":"CVE-2026-6406"},"packages":[],"prev":{"headline":"Anomify AI \u003c= 0.3.6 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'anomify_api_key' Parameter","id":"CVE-2026-6404"},"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":"Attackers can trick admins into submitting forged requests to inject malicious scripts, leading to code execution and privilege escalation in the Anomify AI plugin.","url":"https://insights.sbomify.com/CVE-2026-6405/"}