# CVE-2025-10705: MxChat – AI Chatbot for WordPress <= 2.4.6 - Unauthenticated Blind Server-Side Request Forgery

> Unauthenticated attackers can force the WordPress server to make arbitrary HTTP requests via the MxChat plugin's PDF processing feature.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wp43-3gf2-97gx

## What is CVE-2025-10705?

CVE-2025-10705 is a medium-severity server-side request forgery vulnerability in MxChat – AI Chatbot & Content Generation for WordPress, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-10705?


## How do I fix CVE-2025-10705?

No fix has been published for CVE-2025-10705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10705 being exploited?

There is no known exploitation of CVE-2025-10705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10705 and fix it if it is affected.

What it is: CVE-2025-10705 is a medium-severity server-side request forgery vulnerability in MxChat – AI Chatbot & Content Generation for WordPress, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10705 in the wild and no public exploit code.

Affected product: MxChat – AI Chatbot & Content Generation for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10705/ (Markdown: https://insights.sbomify.com/CVE-2025-10705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10705
- OSV: https://osv.dev/vulnerability/CVE-2025-10705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10705/
Summaries are generated and may contain mistakes; the official description above is the record.