# CVE-2021-24997: WP Guppy < 1.3 - Sensitive Information Disclosure

> Unauthenticated attackers can access sensitive user data and send messages as arbitrary users via unprotected REST API endpoints in the WP Guppy plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f373-v3ww-mcwj

## What is CVE-2021-24997?

CVE-2021-24997 is a medium-severity missing authorization vulnerability in Unknown WP Guppy, published on 27 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Guppy WordPress plugin before 1.3 does not have any authorisation in some of the REST API endpoints, allowing any user to call them and could lead to sensitive information disclosure, such as usernames and chats between users, as well as be able to send messages as an arbitrary user

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wp-Guppy Wp Guppy.

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

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

## Is CVE-2021-24997 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24997 exists.

Public exploit code:

- WordPress Guppy <=1.1 - Information Disclosure (nuclei): http/cves/2021/CVE-2021-24997.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24997 is a medium-severity missing authorization vulnerability in Unknown WP Guppy, published on 27 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-24997 exists.

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

## Sources

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

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