MxChat CVE-2025-10705

Exploitation requires that the MxChat PDF processing path be reachable via the mxchat_handle_chat_request AJAX action on a WordPress site running MxChat ≤2.4.6; the attacker must supply a URL that the plugin fetches during PDF handling. No authentication, user interaction, or non-default configuration is indicated - the AJAX action is callable by unauthenticated users (PR:N/UI:N). Realistic impact is LIMITED by the blind nature of the SSRF (no response returned to the attacker) and by any outbound network egress filtering: the attack is only materially dangerous where the WordPress server can reach sensitive internal services or a cloud metadata endpoint. Effective exploitation value therefore depends heavily on the victim's network segmentation and egress controls rather than on special plugin settings.

This is a moderate-severity, low-priority issue that should not jump the patch queue despite being remotely and unauthenticatedly reachable. The signals are consistent rather than conflicting: the NVD/Wordfence CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3) correctly reflects that an unauthenticated network attacker can trigger the flaw with low complexity, but the impact is capped at low confidentiality with no integrity or availability effect - appropriate for a BLIND SSRF (CWE-918) where the attacker cannot directly read the response. The EPSS score of 0.29% (20th percentile) reinforces low real-world exploitation likelihood, and there is no public exploit identified at time of analysis and no CISA KEV listing. No SSVC decision point data was supplied in the input. The practical risk is that of an SSRF primitive - internal network/port probing, hitting cloud metadata endpoints, or pivoting to other internal services - rather than direct data theft or code execution on the WordPress host. Net: real but low urgency; prioritize patching where the WordPress host sits adjacent to sensitive internal services or a cloud metadata service (e.g., AWS IMDSv1).

An unauthenticated attacker sends a crafted request to the plugin's mxchat_handle_chat_request AJAX endpoint supplying an attacker-controlled URL to the PDF processing feature, causing the WordPress server to issue an HTTP request to that destination. Because the SSRF is blind, the attacker cannot read the response body directly but can use it to probe internal hosts/ports, reach cloud metadata services, or interact with internal-only endpoints inferred through timing or side effects. No public exploit code is identified at time of analysis.