sales@hackhalt.com

Home / Threats / CVE-2021-24997

Wp Guppy - Information Disclosure (CVE-2021-24997)

CVE-2021-24997

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

CVE-2021-24997

MEDIUM CVSS 6.5 Published 2021-12-27 Updated 2026-06-17
AI Risk Elevated (66/100) Active Exploit: No strong signal Published Exploit: Public exploit references found Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected Components 1
Reference Links 2
AI Risk Engine Elevated (66/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2021-12-27 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-04-11 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 177 days ago

AI enriched 177 days ago (2026-04-11 15:24 UTC)

Technical Summary

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

Potential Impact

Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on published exploit references.

Primary risk drivers: published exploit references

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 66/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Wp Guppy PLUGIN · wp-guppy Affected: < 1.3 Fixed in: 1.3

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Wp Guppy to 1.3 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Restrict REST API in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Require authentication for REST namespaces that do not need to be public, so the API cannot be used to enumerate content and accounts.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Wp Guppy, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Wp Guppy. Versions below 1.3 are vulnerable; that release and later are not.

How do I fix it?

Update Wp Guppy to version 1.3 or later. That is the complete fix. Until you can update, Restrict REST API in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Information Disclosure flaw. An attacker who exploits it can read data they were never meant to see, which is often the first step in a larger attack.