dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-5993

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 →
60/100
Remediation priority · Elevated
Remotely reachable 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 Cliengo – Chatbot plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'update_session' function in all versions up to, and including, 3.0.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the session token of 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 confidence

The Cliengo WordPress plugin contains a broken access control vulnerability where the 'update_session' function lacks proper capability verification. This allows any authenticated user with Subscriber-level permissions or higher to modify chatbot session tokens without authorization, enabling unauthorized modification of application data.

MitigationUpdate the plugin to version 3.0.3 or later which implements proper capability checks on the update_session function to ensure only authorized users can modify session data.

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

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

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

  1. Confirm Cliengo plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Cliengo' in the list of installed plugins. Note whether it is active or inactive.
    Affected if The Cliengo plugin is installed and active
  2. Identify the installed plugin version
    In the Plugins list, find the Cliengo plugin and check the version number displayed below the plugin name. Compare this to the fixed version 3.0.3.
    Affected if The installed version is lower than 3.0.3
  3. Verify user roles with Subscriber access exist
    Go to WordPress admin > Users and review the list of user accounts. Check if any users have the 'Subscriber' role assigned.
    Affected if There is at least one user with Subscriber-level permissions
  4. Check if AJAX endpoints are accessible
    Inspect the plugin files (typically in wp-content/plugins/cliengo) for the update_session function and verify the AJAX action is registered without capability checks. Look for add_action('wp_ajax_update_session', ...) or similar without a capability check like current_user_can() before execution.
    Affected if The update_session function is accessible without proper capability verification (versions below 3.0.3)
  5. Test endpoint access with low-privilege account
    If you have a test environment, attempt to access the update_session AJAX endpoint using a user with only Subscriber permissions to confirm unauthorized access is possible.
    Affected if A Subscriber-level user can successfully modify chatbot session tokens

You are affected if the Cliengo plugin is installed with a version lower than 3.0.3 and your site has any users with Subscriber-level permissions or higher.

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 3.0.3 or later which implements proper capability checks on the update_session function to ensure only authorized users can modify session data.

Recommended fix Moderate confidence

Version 3.0.3 or later (upgrade from 3.0.2 to latest available)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Cliengo – Chatbot' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. After updating, verify the plugin is working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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