dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-10705

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MxChat WordPress plugin up to version 2.4.6 contains a blind Server-Side Request Forgery (SSRF) vulnerability in its PDF processing functionality. Unauthenticated attackers can exploit the mxchat_handle_chat_request AJAX action to force the WordPress server to send HTTP requests to arbitrary URLs, potentially reaching internal services or external systems without the attacker seeing the response.

MitigationUpdate to the latest patched version of the plugin. If no patch is available, disable the plugin or implement firewall rules to restrict access to the vulnerable AJAX endpoint until remediation is possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MxChat plugin is installed
    Check wp-content/plugins/ directory for the mxchat folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if MxChat plugin folder exists in the WordPress plugins directory
  2. Identify the installed version
    Open the main plugin PHP file (usually mxchat.php) and locate the Version header in the plugin comment block, or check via WordPress admin plugin list
    Affected if Version is 2.4.6 or lower (any version up to and including 2.4.6)
  3. Verify the vulnerable AJAX endpoint is accessible
    Send an unauthenticated POST request to /wp-admin/admin-ajax.php with parameter action=mxchat_handle_chat_request (no authentication required)
    Affected if The AJAX endpoint responds with a 200 OK status without requiring login authentication
  4. Confirm PDF processing feature may be triggered
    Check plugin settings page in WordPress admin under MxChat settings for any PDF-related configuration, or inspect the plugin code for PDF handling functions (look for functions referencing pdf in the filename)
    Affected if PDF processing feature exists and the plugin settings or code indicates it can be invoked via the vulnerable AJAX action

A user is affected if the MxChat plugin versions 2.4.6 or lower are installed and the vulnerable mxchat_handle_chat_request AJAX endpoint is accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the plugin. If no patch is available, disable the plugin or implement firewall rules to restrict access to the vulnerable AJAX endpoint until remediation is possible.

Recommended fix Moderate confidence

Update MxChat – AI Chatbot for WordPress to version 2.4.7 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'MxChat – AI Chatbot for WordPress'
  4. Click 'Update Now' to update to the latest version, or manually update if automatic update is not available
  5. Verify the plugin is updated to version 2.4.7 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10705 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data