CVE-2021-24997: The WP Guppy WordPress plugin before 1.3 does not have any authorisation in some of the REST API endpoints, al

Q: How do I fix CVE-2021-24997?

wp guppy: upgrade to 1.3. Exact commands for each OS are on this page.

Q: Is CVE-2021-24997 being exploited?

CVE-2021-24997 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-2021-24997 affect?

CVE-2021-24997 affects wp guppy. Severity is medium (CVSS 6.5). 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 wel

Q: How urgent is CVE-2021-24997?

Priority 54/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 6.5REMOTEUPGRADE

CVE-2021-24997 is a medium-severity flaw (CVSS 6.5) affecting wp guppy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.8% (top 14%)
CISA exploited list	No
Weakness	CWE-862
Published	2021-12-27
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: wp-guppy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-12-27 11:15 UTCPublished CVE record published
2026-06-17 03:41 UTCUpdated Record last modified

wp-guppy wp guppy UPGRADE

Affected: < 1.3

Fixed in: 1.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-guppy || rpm -q wp-guppy || wp-guppy --version

2. UPGRADE to 1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-guppy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-guppy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: WordPress Guppy <=1.1 - Information Disclosure

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-2021-24997?

wp guppy: upgrade to 1.3. Exact commands for each OS are on this page.

Is CVE-2021-24997 being exploited?

CVE-2021-24997 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-2021-24997 affect?

CVE-2021-24997 affects wp guppy. Severity is medium (CVSS 6.5). 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 wel

How urgent is CVE-2021-24997?

Priority 54/100. Public exploit reference; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs