CVE-2026-107654
One to one user Chat by WPGuppy <= 1.1.6 - Unauthenticated SQL Injection via 'userId' Parameter
Description
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.
INFO
Published Date :
Nov. 21, 2026, 11:30 a.m.
Last Modified :
Nov. 21, 2026, 11:30 a.m.
Remotely Exploit :
Yes !
Source :
Wordfence
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | MITRE-CVE |
Solution
- Update the WPGuppy plugin to version 1.1.7 or later.
- Ensure all user input is properly escaped.
- Use prepared statements for all SQL queries.
- Validate JWTs with a securely generated secret.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-107654 vulnerability anywhere in the article.