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

CVE-2024-11813

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 Pulsating Chat Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.1. This is due to missing or incorrect nonce validation on the amin_chat_button_settings_page() function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Pulsating Chat Button WordPress plugin fails to validate nonces in the amin_chat_button_settings_page() function, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables injection of malicious web scripts through plugin settings that are subsequently stored and executed when other users visit affected pages.

MitigationUpdate to the latest version of the plugin (1.4.2 or later). If no update is available, deactivate and remove the plugin until a patch is released. Review existing plugin settings for any injected malicious scripts.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 and navigate to Plugins > Installed Plugins. Look for 'Pulsating Chat Button' in the list of active plugins.
    Affected if The plugin is installed and active, exposing the vulnerable settings function.
  2. Check installed version
    In the plugins list, find the Pulsating Chat Button plugin and note the version number displayed below the plugin name. Compare this version to the fixed version 1.4.2.
    Affected if Version is lower than 1.4.2, meaning the nonce validation vulnerability is present.
  3. Inspect plugin settings for malicious scripts
    Navigate to the plugin settings page (usually under Settings or the plugin's own menu item). Examine all text fields, button labels, chat messages, or URL fields for suspicious JavaScript code, encoded characters, or unexpected script tags.
    Affected if Any settings contain injected JavaScript or HTML script tags that were not intentionally configured by an administrator.
  4. Review WordPress options for unauthorized changes
    Use a database query or plugin like WP-CLI to inspect the wp_options table for the plugin's option names. Check option_value fields for base64-encoded strings, eval() calls, or script tags.
    Affected if Option values contain unexpected code patterns or appear to have been modified without legitimate admin action.

A user is affected if the Pulsating Chat Button plugin is installed with a version lower than 1.4.2 OR if plugin settings contain injected malicious scripts regardless of version.

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 to the latest version of the plugin (1.4.2 or later). If no update is available, deactivate and remove the plugin until a patch is released. Review existing plugin settings for any injected malicious scripts.

Recommended fix Moderate confidence

1.4.2 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Pulsating Chat Button' plugin
  4. If an update is available, click 'Update Now' to upgrade to version 1.4.2 or later
  5. Alternatively, navigate to Plugins > Add New > Upload and upload the latest version of the plugin from wordpress.org/plugins/pulsating-chat-button

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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