# CVE-2021-24864: WP Cloudy < 4.4.9 - Admin+ SQL Injection

> An authenticated admin can exploit SQL injection in the WP Cloudy plugin to read or modify database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 28 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pm48-wg42-xj5r

## What is CVE-2021-24864?

CVE-2021-24864 is a high-severity SQL injection vulnerability in Unknown WP Cloudy, weather plugin, published on 28 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Cloudy, weather plugin WordPress plugin before 4.4.9 does not escape the post_id parameter before using it in a SQL statement in the admin dashboard, leading to a SQL Injection issue

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Wpscan Wp Cloudy.

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

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

## Is CVE-2021-24864 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24864 is a high-severity SQL injection vulnerability in Unknown WP Cloudy, weather plugin, published on 28 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-2021-24864 in the wild and no public exploit code.

Affected product: Unknown WP Cloudy, weather plugin. 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-24864/ (Markdown: https://insights.sbomify.com/CVE-2021-24864/index.md)
```

## Sources

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

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