One to one user Chat by WPGuppy: A security weakness
One to one user Chat by WPGuppy is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- One to one user Chat by WPGuppy
- Plugin slug
wpguppy-lite- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Feb 14, 2026
This CVE was published Feb 14, 2026 and is one of 6 known issues for this plugin.
Update, patch or deactivate.
Update One to one user Chat by WPGuppy to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N