Plugins · anycomment · data as of 2026-11-04
Is AnyComment safe? Known vulnerabilities and latest version
- Status
- Closed 2026-10-05
- Known issues on record
- 8
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate anycomment && wp plugin delete anycomment
Check your version
Known vulnerabilities
8 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 8 record(s) do not state which versions are affected.
high 7.2 CVE-2026-103422 · published 2026-10-14
Stored cross-site scripting (XSS) in AnyComment (0.3.6 and older)
- Affected
- 0.3.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
medium 4.3 CVE-2025-62874 · published 2025-12-31
Missing authorization check in AnyComment (0.3.6 and older)
- Affected
- 0.3.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in Alexander AnyComment anycomment allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AnyComment: from n/a through <= 0.3.6.
high 7.5 CVE-2025-60240 · published 2025-11-06
File inclusion in AnyComment (0.3.6 and older)
- Affected
- 0.3.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Alexander AnyComment anycomment allows PHP Local File Inclusion.This issue affects AnyComment: from n/a through <= 0.3.6.
high 8.5 CVE-2025-48091 · published 2025-10-22
SQL injection in AnyComment (0.3.6 and older)
- Affected
- 0.3.6 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Alexander AnyComment anycomment allows SQL Injection.This issue affects AnyComment: from n/a through <= 0.3.6.
high 8.8 CVE-2022-0134 · published 2022-02-21
Cross-site request forgery (CSRF) in AnyComment (older than 0.2.18)
- Affected
- older than 0.2.18
- Fixed in
- 0.2.18
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The AnyComment WordPress plugin before 0.2.18 does not have CSRF checks in the Import and Revert HyperComments features, allowing attackers to make logged in admin perform such actions via a CSRF attack
low 3.1 CVE-2022-0279 · published 2022-02-21
Security issue in AnyComment (older than 0.2.18)
- Affected
- older than 0.2.18
- Fixed in
- 0.2.18
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- NVD analysis · score by NVD
Details from the advisory
The AnyComment WordPress plugin before 0.2.18 is affected by a race condition when liking/disliking a comment/reply, which could allow any authenticated user to quickly raise their rating or lower the rating of other users
medium 6.1 CVE-2021-24838 · published 2022-01-17
Open redirect in AnyComment (older than 0.3.5)
- Affected
- older than 0.3.5
- Fixed in
- 0.3.5
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect parameter to the wp_redirect() function without being validated first, leading to an Open Redirect issue, which according to the vendor, is a feature.
medium 6.1 CVE-2018-21001 · published 2019-08-27
Cross-site scripting (XSS) in AnyComment (older than 0.0.33)
- Affected
- older than 0.0.33
- Fixed in
- 0.0.33
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- NVD analysis · score by NVD
Details from the advisory
The anycomment plugin before 0.0.33 for WordPress has XSS.
Recent activity
- 2026-10-05 — closed on wordpress.org.
- 2026-10-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-103422), fix version not stated.
- 2025-12-31 — Missing authorization check disclosed (CVE-2025-62874), fix version not stated.
- 2025-11-06 — File inclusion disclosed (CVE-2025-60240), fix version not stated.
Get an email when AnyComment has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for AnyComment (anycomment) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (2) · Missing authorization (1) · File inclusion (1) · SQL injection (1) · Cross-site request forgery (CSRF) (1) · Open redirect (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/anycomment (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/anycomment"><img src="https://laskyr.com/plugins/anycomment/badge.svg" alt="AnyComment vulnerability status"></a>