CVE-2022-0279: The AnyComment WordPress plugin before 0.2.18 is affected by a race condition when liking/disliking a comment/

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

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

Q: Is CVE-2022-0279 being exploited?

CVE-2022-0279 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-0279 affect?

CVE-2022-0279 affects anycomment. Severity is low (CVSS 3.1). 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

Q: How urgent is CVE-2022-0279?

Priority 26/100. Public exploit reference

Routine

LOW 3.1UPGRADE

CVE-2022-0279 is a low-severity flaw (CVSS 3.1) 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 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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.1 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-362
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-0279?

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

Is CVE-2022-0279 being exploited?

CVE-2022-0279 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-0279 affect?

CVE-2022-0279 affects anycomment. Severity is low (CVSS 3.1). 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

How urgent is CVE-2022-0279?

Priority 26/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-0134 HIGH 8.8 UPGRADE The AnyComment WordPress plugin before 0.2.18 does not have CSRF checks in the Import and Revert HyperComments
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