One to one user Chat by WPGuppy unauthenticated SQL injection in userId parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The One to one user Chat by WPGuppy plugin for WordPress has an SQL injection flaw in its 'userId' parameter. Remotely, without logging in, an attacker can append their own SQL queries to existing ones and extract sensitive information from the database.
Written by a model
Original 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.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-107654 (One to one user Chat by WPGuppy <= 1.1.6 - Unauthenticated SQL Injection via 'userId' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-107654 (entry last updated 2026-11-21):
Affected:
- amentotechpvtltd One to one user Chat by WPGuppy: through 1.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-107654 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107654 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e25f3bd0-16d8-48e1-b822-40dbe681c4bc?source=cve
- https://plugins.trac.wordpress.org/browser/wpguppy-lite/trunk/includes/class-wp-guppy-model.php#L253
- https://plugins.trac.wordpress.org/browser/wpguppy-lite/trunk/includes/class-wp-guppy-rest-api.php#L1785
- https://plugins.trac.wordpress.org/browser/wpguppy-lite/trunk/includes/class-wp-guppy-rest-api.php#L754
- https://plugins.trac.wordpress.org/browser/wpguppy-lite/trunk/includes/class-wp-guppy-rest-api.php#L401
- https://downloads.wordpress.org/plugin/wpguppy-lite.1.1.7.zip
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-107654
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107654"}.Affected versions
- amentotechpvtltd One to one user Chat by WPGuppythrough 1.1.6
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
Questions about CVE-2026-107654
Is CVE-2026-107654 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-107654?
One to one user Chat by WPGuppy: through 1.1.6.
Source: cve.now feed data
Related
- CVE-2025-6792One to one user Chat by WPGuppy <= 1.1.4 - Unauthenticated Information Disclosure via Chat Message Interception
- CVE-2026-129175U.S Department of the Interior Unstable Slope Management Program unauthenticated SQL Injection
- CVE-2026-134293SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks
- CVE-2026-131701WordPress WP Media folder plugin <= 6.2.8 - SQL Injection vulnerability
- CVE-2026-131705WordPress ProfileGrid plugin <= 6.0.0.6 - SQL Injection vulnerability
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
No corrections so far. Something wrong on this page? Report an error.