dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12043

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-25
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 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.

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 Autochat Automatic Conversation WordPress plugin versions up to 1.1.9 exposes an AJAX endpoint 'wp_ajax_nopriv_auycht_saveCid' accessible to unauthenticated users without any capability verification, allowing attackers to arbitrarily connect or disconnect client IDs.

MitigationUpdate the plugin to version 1.2.0 or later which implements proper capability checks on the AJAX endpoint, or add an authorization check (current_user_can) to the handler if no patch is available.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Autochat Automatic Conversation' in the list
    Affected if Plugin is not installed or not found
  2. Check plugin version
    In the Plugins list, click on the plugin details or view the plugin header in /wp-content/plugins/autochat-automatic-conversation/auto-chat.php to find the Version: X.X.X entry
    Affected if Version is 1.1.9 or lower (the affected range)
  3. Confirm plugin is active
    In WordPress admin Plugins list, ensure the plugin shows as 'Active' rather than 'Inactive'
    Affected if Plugin is active with vulnerable version
  4. Verify endpoint accessibility
    Send a test POST request to yoursite.com/wp-admin/admin-ajax.php with action=auycht_saveCid (no authentication required) - a 200 response indicates the exposed endpoint exists
    Affected if Endpoint responds without requiring authentication

User is affected if the Autochat Automatic Conversation plugin is active at version 1.1.9 or lower, exposing the unauthenticated AJAX endpoint wp_ajax_nopriv_auycht_saveCid.

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 the plugin to version 1.2.0 or later which implements proper capability checks on the AJAX endpoint, or add an authorization check (current_user_can) to the handler if no patch is available.

Recommended fix Moderate confidence

Version 1.2.0 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Autochat Automatic Conversation' plugin
  4. Check if an update to version 1.2.0 or higher is available
  5. If update available, click 'Update Now' to install the patched version
  6. If no update appears, manually download version 1.2.0 or later from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the wp_ajax_nopriv_auycht_saveCid endpoint now requires authentication

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12043 — 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-12043 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