# CVE-2022-0279: AnyComment < 0.2.18 - Comment Rating Increase/Decrease via Race Condition

> Authenticated users can exploit a race condition to manipulate comment ratings, requiring an upgrade to the AnyComment plugin.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g7w5-4hph-r98m

## What is CVE-2022-0279?

CVE-2022-0279 is a low-severity vulnerability in Unknown AnyComment, published on 21 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2022-0279?

It affects 1 product.


Products: Bologer Anycomment.

## How do I fix CVE-2022-0279?

No fix has been published for CVE-2022-0279 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0279 being exploited?

There is no known exploitation of CVE-2022-0279 in the wild and no public exploit code.

## Other vulnerabilities in Unknown AnyComment

- [CVE-2022-0134](https://insights.sbomify.com/CVE-2022-0134/): AnyComment < 0.2.18 - Arbitrary HyperComments Import/Revert via CSRF (high 8.8)
- [CVE-2021-24838](https://insights.sbomify.com/CVE-2021-24838/): AnyComment < 0.3.5 - Open Redirect (medium 6.1)
- [CVE-2018-21001](https://insights.sbomify.com/CVE-2018-21001/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0279 and fix it if it is affected.

What it is: CVE-2022-0279 is a low-severity vulnerability in Unknown AnyComment, published on 21 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0279 in the wild and no public exploit code.

Affected product: Unknown AnyComment. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0279/ (Markdown: https://insights.sbomify.com/CVE-2022-0279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0279
- OSV: https://osv.dev/vulnerability/CVE-2022-0279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0279/
Summaries are generated and may contain mistakes; the official description above is the record.