# CVE-2021-24894: Reviews Plus < 1.2.14 - Subscriber+ Reviews DoS

> An authenticated user can cause a Denial of Service in the review section by submitting an invalid long integer rating.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 23 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cg9v-q8q5-prwx

## What is CVE-2021-24894?

CVE-2021-24894 is a medium-severity denial of service vulnerability in Unknown Reviews Plus, published on 23 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Reviews Plus WordPress plugin before 1.2.14 does not validate the submitted rating, allowing submission of long integer, causing a Denial of Service in the review section when an authenticated user submit such rating and the reviews are set to be displayed on the post/page

Weakness: CWE-20 (Improper Input Validation), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2021-24894?

It affects 1 product.


Products: Implecode Reviews Plus.

## How do I fix CVE-2021-24894?

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

## Is CVE-2021-24894 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24894 and fix it if it is affected.

What it is: CVE-2021-24894 is a medium-severity denial of service vulnerability in Unknown Reviews Plus, published on 23 Nov 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24894 in the wild and no public exploit code.

Affected product: Unknown Reviews Plus. 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-2021-24894/ (Markdown: https://insights.sbomify.com/CVE-2021-24894/index.md)
```

## Sources

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

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