dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-37923

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in cliengo Cliengo – Chatbot cliengo allows Cross Site Request Forgery.This issue affects Cliengo – Chatbot: from n/a through <= 3.0.4.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Cliengo WordPress chatbot plugin allows attackers to trick authenticated administrators into performing unintended actions. The plugin lacks proper anti-CSRF token validation on state-changing requests, enabling malicious requests to be executed without the user's consent.

MitigationImplement WordPress nonces (wp_nonce_field) on all forms and AJAX actions, and verify nonce validation in request handlers to prevent CSRF attacks.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Cliengo plugin installation
    Navigate to WordPress admin > Plugins and check if the Cliengo plugin is installed and active, or inspect the /wp-content/plugins/ directory for a cliengo folder
    Affected if The Cliengo plugin is installed and active on the WordPress site
  2. Identify the installed version
    In WordPress admin > Plugins, find Cliengo and note the version number displayed, or open the main plugin file (e.g., cliengo.php) and look for the Version header comment
    Affected if The installed version lacks the fix or is unknown/older than a patched release
  3. Check for nonce implementation in AJAX handlers
    Examine the plugin source code for AJAX action handlers (wp_ajax_* hooks) and verify if they include wp_verify_nonce or check_admin_referer calls before processing state-changing requests
    Affected if State-changing AJAX actions process requests without validating WordPress nonces
  4. Inspect form handlers for nonce validation
    Review plugin PHP files for form submissions (POST/GET requests that modify data) and confirm that each includes nonce verification before executing state-changing logic
    Affected if Forms that modify plugin settings or user data lack wp_nonce_field or equivalent validation
  5. Verify nonce field presence in plugin forms
    View the source HTML of any Cliengo plugin admin pages/forms and check if they include a hidden nonce field (typically named _wpnonce or similar)
    Affected if Plugin forms render without any nonce token fields

A user is affected if the Cliengo WordPress plugin is installed and its state-changing requests (AJAX handlers or form submissions) do not validate WordPress nonces before executing actions.

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

Implement WordPress nonces (wp_nonce_field) on all forms and AJAX actions, and verify nonce validation in request handlers to prevent CSRF attacks.

Recommended fix Moderate confidence

Plugin version 3.0.5 or higher

  1. Check the WordPress admin dashboard for plugin updates
  2. Navigate to Plugins > All Plugins > Cliengo – Chatbot
  3. If update to version 3.0.5 or higher is available, click Update Now
  4. Wait for the update to complete and verify the plugin is running version 3.0.5 or higher
  5. Test that the chatbot functionality continues to work correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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