MxChat – AI Chatbot for WordPress <= 2.4.6 - Unauthenticated Blind Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 2.4.7
- Affected Plugin
- MxChat – AI Chatbot & Content Generation for WordPress
- Affected Version
<= 2.4.6- CVSS
- 5.3Medium
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2025-10705
At a glance
CVE-2025-10705 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the MxChat WordPress plugin, affecting versions <= 2.4.6. 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 2.4.7; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The MxChat – AI Chatbot for WordPress plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.4.6. This is due to insufficient validation of user-supplied URLs in the PDF processing functionality. This makes it possible for unauthenticated attackers to make the WordPress server perform HTTP requests to arbitrary destinations via the mxchat_handle_chat_request AJAX action.
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-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in MxChat <= 2.4.6 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For MxChat the fix is 2.4.7: builds <= 2.4.6 are affected, anything from 2.4.7 onward is not.
Remediation
Update to version 2.4.7, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MxChat 2.4.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MxChat – AI Chatbot & Content Generation for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C