CVE-2026-6405
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk6th percentile - higher than 6% of all known CVEs
Summary
The WordPress plugin Anomify AI – Anomaly Detection and Alerting up to version 0.3.6 is vulnerable to Cross-Site Request Forgery (CSRF) leading to Stored Cross-Site Scripting (XSS). Missing nonce verification in the settings page handler and insufficient output escaping in the admin_options.php template allow unauthenticated attackers to inject malicious scripts by tricking an administrator.
Risk Assessment
An attacker can modify plugin settings and inject a persistent script that executes in the administrator's browser every time the settings page is visited, potentially leading to admin account takeover.
Recommendation
Update the Anomify AI plugin to the latest available version. Add nonce verification to settings forms and use the esc_attr() function for output encoding.
Original NVD description (English source)
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.