CVE-2022-0134: The AnyComment WordPress plugin before 0.2.18 does not have CSRF checks in the Import and Revert HyperComments

Q: How do I fix CVE-2022-0134?

anycomment: upgrade to 0.2.18. Exact commands for each OS are on this page.

Q: Is CVE-2022-0134 being exploited?

CVE-2022-0134 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-0134 affect?

CVE-2022-0134 affects anycomment. Severity is high (CVSS 8.8). 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

Q: How urgent is CVE-2022-0134?

Priority 49/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-0134 is a high-severity flaw (CVSS 8.8) affecting anycomment. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-02-21
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: bologer

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-02-21 11:15 UTCPublished CVE record published
2026-06-17 04:20 UTCUpdated Record last modified

bologer anycomment UPGRADE

Affected: < 0.2.18

Fixed in: 0.2.18

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy anycomment || rpm -q anycomment || anycomment --version

2. UPGRADE to 0.2.18 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade anycomment

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade anycomment

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-0134?

anycomment: upgrade to 0.2.18. Exact commands for each OS are on this page.

Is CVE-2022-0134 being exploited?

CVE-2022-0134 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-0134 affect?

CVE-2022-0134 affects anycomment. Severity is high (CVSS 8.8). 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

How urgent is CVE-2022-0134?

Priority 49/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-0279 LOW 3.1 UPGRADE The AnyComment WordPress plugin before 0.2.18 is affected by a race condition when liking/disliking a comment/
CVE-2021-24838 MEDIUM 6.1 UPGRADE The AnyComment WordPress plugin before 0.3.5 has an API endpoint which passes user input via the redirect para

References

← Back to latest CVEs