The Autochat Automatic Conversation plugin for WordPress is vulnerable to unauthorized modification of data due to a
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 18 Nov 2026, 02:31 UTC
- Affects
- all up to 1.1.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
AI-suggested
Since the vulnerability arises from a missing capability check, users should monitor the vendor's advisory for updates and apply any forthcoming patches promptly. Until a fix is available, restricting access to the AJAX endpoint via web application firewall rules or other access controls may help mitigate exploitation risk.
Description
The Autochat Automatic Conversation plugin for WordPress contains a vulnerability in all versions up to 1.1.9 due to a missing capability check on the 'wp_ajax_nopriv_auycht_saveCid' AJAX endpoint. This flaw allows unauthenticated attackers to modify client IDs by connecting or disconnecting them without authorization.