CVE-2024-5992
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 · uneditedThe Cliengo – Chatbot plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_chatbot_token' and 'update_chatbot_position' functions in all versions up to, and including, 3.0.2. This makes it possible for unauthenticated attackers to change chatbot settings, which can lead to unavailability or other changes to the chatbot.
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 confidenceThe Cliengo WordPress plugin lacks capability checks on AJAX actions 'update_chatbot_token' and 'update_chatbot_position', allowing unauthenticated users to directly modify chatbot configuration settings via insecure direct object references.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cliengo plugin is installedCheck the WordPress plugins directory for the cliengo plugin folder, or use WP-CLI: wp plugin list --name=cliengoAffected if Cliengo plugin is installed and active
-
Identify installed Cliengo plugin versionRead the main plugin file (e.g., wp-content/plugins/cliengo/src/index.php or cliengo.php) and look for the version comment header, or use: wp plugin get cliengo --format=jsonAffected if Version is below 3.0.3 or version cannot be determined (plugin may be unpatched)
-
Check if vulnerable AJAX actions exist in plugin codeSearch plugin files for 'update_chatbot_token' and 'update_chatbot_position' function definitions, or grep for add_action('wp_ajax_update_chatbot_token') and similar hooksAffected if These AJAX action handlers exist in the plugin without capability checks
-
Verify AJAX endpoints accept unauthenticated requestsSend a POST request to /wp-admin/admin-ajax.php with action=update_chatbot_token or action=update_chatbot_position without authentication cookiesAffected if The AJAX endpoints respond (even with error) to unauthenticated requests rather than returning 403 or requiring login
User is affected if Cliengo plugin version is below 3.0.3 and the vulnerable AJAX endpoints are accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the Cliengo plugin to version 3.0.3 or later which implements proper authorization checks on the affected functions.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5992 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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