HomeWordPress vulnerabilitiesOne to one user Chat by WPGuppy
One to one user Chat by WPGuppy vulnerabilities
One to one user Chat by WPGuppy has 2 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 2
- Active installs
- 500+
- Latest version
- 1.1.6
- Last updated
- 12 Mar 2026
- Most recent
- 21 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-107654 | High 7.5 | Up to 1.1.6 | No fixed version yet | 1 d ago |
| Broken access control CVE-2025-6792 | Medium 5.3 | Up to 1.1.4 | Fixed in a later version (latest 1.1.6) | 14 Feb 2026 |
Read the published descriptions
- CVE-2026-107654, 21 Nov 2026
- The One to one user Chat by WPGuppy plugin for WordPress is vulnerable to generic SQL Injection via the 'userId' parameter in all versions up to, and including, 1.1.6 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The plugin's permission callback is trivially bypassed because it validates a JWT that the plugin itself signs using an attacker-supplied value from the guppy_guest_account cookie, and the guest code path (userType=0) skips the get_userdata() check that would confirm the userId corresponds to a real WordPress user. CVE record
- CVE-2025-6792, 14 Feb 2026
- 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 record
What to do if you run One to one user Chat by WPGuppy
If you run One to one user Chat by WPGuppy, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new One to one user Chat by WPGuppy vulnerabilities
Free. We email you when a new vulnerability is published for One to one user Chat by WPGuppy, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.