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

CVE-2024-12541

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-07
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
The Chative Live chat and Chatbot plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing or incorrect nonce validation on the add_chative_widget_action() function. This makes it possible for unauthenticated attackers to change the channel ID or organization ID via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This could lead to redirecting the live chat widget to an attacker-controlled channel.

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 Chative Live Chat plugin for WordPress versions up to 1.1 lacks proper nonce validation on the add_chative_widget_action() function, allowing unauthenticated attackers to forge administrative requests. By tricking a logged-in administrator into clicking a malicious link, an attacker can modify the channel ID or organization ID settings, redirecting the live chat widget to an attacker-controlled endpoint.

MitigationImplement proper nonce validation on the add_chative_widget_action() function and review other administrative actions in the plugin for similar CSRF vulnerabilities.

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. Confirm plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Chative Live Chat'. Check the version number displayed there. Compare against the affected range: versions up to and including 1.1 are vulnerable.
    Affected if The installed version is 1.1 or lower.
  2. Locate the vulnerable function in plugin code
    Access the plugin files via WP dashboard > Plugins > Plugin Editor, or via FTP/shell. Look for a file containing the function 'add_chative_widget_action'. This is typically in the main plugin file or an admin settings file.
    Affected if The function exists in the codebase.
  3. Verify nonce validation is missing
    Within the add_chative_widget_action() function, search for 'nonce', 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer'. If none of these validation calls are present, the function lacks CSRF protection.
    Affected if The function contains no nonce verification logic.
  4. Inspect current widget settings for tampering
    In WordPress admin, navigate to the Chative Live Chat settings page (usually under Settings or a dedicated Chative menu). Check the Channel ID and Organization ID fields for any unexpected or suspicious values.
    Affected if The Channel ID or Organization ID points to an unrecognized or external endpoint.

A user is affected if they have Chative Live Chat version 1.1 or lower installed AND the add_chative_widget_action function lacks nonce validation, regardless of whether settings have been altered.

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 proper nonce validation on the add_chative_widget_action() function and review other administrative actions in the plugin for similar CSRF vulnerabilities.

Recommended fix Moderate confidence

1.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Chative Live chat and Chatbot' plugin
  4. 4. If an update is available, click 'Update Now' to install version 1.2 or later
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
  6. 6. Verify the update was successful by checking the plugin version

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-12541 — 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-12541 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