CVE-2025-12585 json
MxChat – AI Chatbot for WordPress <= 2.5.5 - Unauthenticated Information Exposure
published 2025-12-03 11 mo ago modified 2026-10-18 21 d ago also EUVD-2025-200727
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
The MxChat – AI Chatbot for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.5.5 via upload filenames. This makes it possible for unauthenticated attackers to extract session values that can subsequently be used to access conversation data.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- ryankozak.com https://ryankozak.com/posts/cve-2025-12585/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- mxchat MxChat – AI Chatbot & Content Generation for WordPress
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
-
ryankozak.com
/posts/cve-2025-12585/
exploit
- wordfence.com /threat-intel/vulnerabilities/id/7cf1a90d-6157-40e7-aed8-4d18bc22432d?source=cve
- plugins.trac.wordpress.org /browser/mxchat-basic/trunk/includes/class-mxchat-integrator.php#L107
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3406402%40mxchat-basic&new=3406402%40mxchat-basic&sfp_email=&sf
- github.com /d0n601/CVE-2025-12585
- ryankozak.com /posts/cve-2025-12585
Sources
- CVE List CVE-2025-12585
- NVD CVE-2025-12585
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.