HomeWordPress vulnerabilitiesAnyComment
AnyComment vulnerabilities
AnyComment has 4 known vulnerabilities in this database. The most recent published record is dated 21 Feb 2022.
- Known vulnerabilities
- 4
- Active installs
- 5,000+
- Latest version
- 0.3.6
- Last updated
- 14 May 2022
- Most recent
- 21 Feb 2022
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2022-0134 | High 8.8 | Before 0.2.18 | Fixed in 0.2.18 | 21 Feb 2022 |
| Security weakness CVE-2022-0279 | Low 3.1 | Before 0.2.18 | Fixed in 0.2.18 | 21 Feb 2022 |
| Open redirect CVE-2021-24838 | Medium 6.1 | Before 0.3.5 | Fixed in 0.3.5 | 17 Jan 2022 |
| Cross-site scripting (XSS) CVE-2018-21001 | Medium 6.1 | Before 0.0.33 | Fixed in 0.0.33 | 27 Aug 2019 |
Read the published descriptions
- CVE-2022-0134, 21 Feb 2022
- 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 CVE record
- CVE-2022-0279, 21 Feb 2022
- 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 CVE record
- CVE-2021-24838, 17 Jan 2022
- 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. CVE record
- CVE-2018-21001, 27 Aug 2019
- The anycomment plugin before 0.0.33 for WordPress has XSS. CVE record
What to do if you run AnyComment
If you run AnyComment, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new AnyComment vulnerabilities
Free. We email you when a new vulnerability is published for AnyComment, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.