Strategic Overview
- Status
- Patched in 1.1.1
- Affected Plugin
- One to one user Chat by WPGuppy
- Affected Version
<= 1.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-24643
At a glance
CVE-2025-24643 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the One to one user Chat by WPGuppy WordPress plugin, affecting versions <= 1.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.1; sites on affected versions should update now. Disclosed January 2025, reported by l8BL.
Vulnerability Overview
The One to one user Chat by WPGuppy plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.1.0. This is due to the plugin not properly verifying a user's identity prior to using wp_set_current_user(). This makes it possible for unauthenticated attackers to spoof other users and modify some of the plugin's settings.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
One to one user Chat by WPGuppy <= 1.1.0 carries this weakness at wp_set_current_user(), and reaching it takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For One to one user Chat by WPGuppy the fix is 1.1.1: builds <= 1.1.0 are affected, anything from 1.1.1 onward is not.
Remediation
Update to version 1.1.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: One to one user Chat by WPGuppy 1.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in One to one user Chat by WPGuppy
- 9.8CVE-2024-49222: WPGuppy <= 1.1.0 PHP Object Injection
CVE-2024-49222 - 8.8CVE-2024-56280: WPGuppy <= 1.1.0 Privilege Escalation
CVE-2024-56280 - 6.5CVE-2025-30775: WPGuppy <= 1.1.3 SQL Injection
CVE-2025-30775 - 5.3CVE-2025-6792: One to one user Chat by WPGuppy Information Disclosure
CVE-2025-6792 - 5.3CVE-2025-49910: WPGuppy <= 1.1.4 Missing Authorization
CVE-2025-49910
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C