AnyComment <= 0.3.6 - Unauthenticated Stored Cross-Site Scripting via 'email' Parameter
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- AnyComment
- Affected Version
<= 0.3.6- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-103422
At a glance
CVE-2026-103422 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the AnyComment WordPress plugin, affecting versions <= 0.3.6. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2026, reported by Kevin Whelan.
Vulnerability Overview
The AnyComment plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'email' parameter in versions up to, and including, 0.3.6. This is due to insufficient input sanitization on the public /wp-json/anycomment/v1/subscribe REST endpoint and missing output escaping in AnyCommentSubscriptionsTable::column_default(), which returns the stored email verbatim into an HTML <td> when the subscription's user_ID does not resolve to an existing WP_User. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the AnyComment → Subscriptions admin page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
AnyComment <= 0.3.6 carries this weakness at email, and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. No fixed build of this plugin is recorded for AnyComment yet, so installs running <= 0.3.6 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AnyComment
- 8.8CVE-2022-0134: AnyComment <= 0.2.17 Cross-Site Request Forgery
CVE-2022-0134 - 8.1CVE-2025-60240: AnyComment <= 0.3.6 Local File Inclusion
CVE-2025-60240 - 6.5CVE-2025-48091: AnyComment <= 0.3.6 SQL Injection
CVE-2025-48091 - 5.4CVE-2021-24838: AnyComment <= 0.3.4 Open Redirect
CVE-2021-24838 - 5.3CVE-2022-0279: AnyComment <= 0.2.17 Race Condition
CVE-2022-0279 - 4.3CVE-2025-62874: AnyComment <= 0.3.6 Missing Authorization
CVE-2025-62874
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C