Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12043: CWE-862 Missing Authorization in autochat Autochat Automatic Conversation

0
Medium
VulnerabilityCVE-2025-12043cvecve-2025-12043cwe-862
Published: Tue Nov 25 2025 (11/25/2025, 07:28:18 UTC)
Source: CVE Database V5
Vendor/Project: autochat
Product: Autochat Automatic Conversation

Description

The Autochat Automatic Conversation plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wp_ajax_nopriv_auycht_saveCid' AJAX endpoint in all versions up to, and including, 1.1.9. This makes it possible for unauthenticated attackers to connect and disconnect the client ID.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 19:56:46 UTC

Technical Analysis

The CVE-2025-12043 vulnerability affects the Autochat Automatic Conversation plugin for WordPress, specifically versions up to and including 1.1.9. The root cause is a missing capability check on the AJAX endpoint 'wp_ajax_nopriv_auycht_saveCid', which is designed to handle client ID connections and disconnections. Because this endpoint lacks proper authorization, unauthenticated attackers can invoke it remotely without any credentials or user interaction, enabling them to arbitrarily connect or disconnect client IDs. This unauthorized modification impacts the integrity of the data managed by the plugin, potentially disrupting chat sessions or enabling attackers to manipulate client identifiers for further malicious activities. The vulnerability does not affect confidentiality or availability directly, as it does not expose sensitive data or cause denial of service. The CVSS 3.1 base score is 5.3, reflecting medium severity, with attack vector as network, low attack complexity, no privileges required, and no user interaction needed. No patches or official fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability is categorized under CWE-862 (Missing Authorization), highlighting the absence of proper access control checks on sensitive operations.

Potential Impact

The primary impact of CVE-2025-12043 is unauthorized integrity modification within the Autochat plugin's client ID management. Attackers can manipulate client IDs by connecting or disconnecting them without authentication, potentially disrupting chat functionalities or enabling further exploitation through crafted client sessions. Although this does not directly compromise confidential information or cause denial of service, it undermines trust in the plugin's operation and may facilitate secondary attacks such as session hijacking or impersonation if combined with other vulnerabilities. Organizations relying on Autochat for customer interaction may experience degraded user experience or reputational damage if attackers exploit this flaw. The ease of exploitation and network accessibility increase the risk, especially for websites with high traffic or critical customer engagement. The absence of known exploits reduces immediate threat but does not eliminate future risk, making timely mitigation important.

Mitigation Recommendations

To mitigate CVE-2025-12043, organizations should first verify if they are using the Autochat Automatic Conversation plugin, particularly versions up to 1.1.9. Since no official patches are currently available, administrators should consider the following specific actions: 1) Temporarily disable or restrict access to the vulnerable AJAX endpoint 'wp_ajax_nopriv_auycht_saveCid' by implementing web application firewall (WAF) rules that block unauthenticated requests to this endpoint. 2) Apply custom code or plugin modifications to enforce capability checks on this AJAX action, ensuring only authorized users can invoke it. 3) Monitor web server logs for suspicious requests targeting this endpoint to detect potential exploitation attempts. 4) Limit plugin usage to trusted environments or isolate affected sites behind additional authentication layers. 5) Stay updated with vendor announcements for official patches or updates and apply them promptly once released. 6) Conduct regular security assessments of WordPress plugins to identify and remediate similar authorization issues proactively.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-21T19:03:42.165Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69255e27292ce6fc00be05cd

Added to database: 11/25/2025, 7:43:35 AM

Last enriched: 2/27/2026, 7:56:46 PM

Last updated: 3/21/2026, 11:18:29 PM

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses