Guest Support <= 1.2.3 - Unauthenticated User Email Disclosure in guest_support_handler AJAX Endpoint
Strategic Overview
- Status
- Patched in 1.3.0
- Affected Plugin
- Guest Support
- Affected Version
<= 1.2.3- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-13660
At a glance
CVE-2025-13660 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Guest Support WordPress plugin, affecting versions <= 1.2.3. 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.3.0; sites on affected versions should update now. Disclosed December 2025, reported by Md. Moniruzzaman Prodhan (NomanProdhan).
Vulnerability Overview
The Guest Support plugin for WordPress is vulnerable to User Email Disclosure in versions up to, and including, 1.2.3. This is due to the plugin exposing a public AJAX endpoint that allows anyone to search for and retrieve user email addresses without any authentication or capability checks. This makes it possible for unauthenticated attackers to enumerate user accounts and extract email addresses via the guest_support_handler=ajax endpoint with the request=get_users parameter.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Guest Support <= 1.2.3 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Guest Support the fix is 1.3.0: builds <= 1.2.3 are affected, anything from 1.3.0 onward is not.
Remediation
Update to version 1.3.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Guest Support 1.3.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Guest Support
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C