dbcve.org
Like Button RatingWordPress extension · Likebtn

CVE-2024-44064

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 2.6.54 or later.
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LikeBtn Like Button Rating likebtn-like-button.This issue affects Like Button Rating: from n/a through <= 2.6.53.

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 scripting (XSS) vulnerability in the LikeBtn Like Button Rating WordPress plugin allows injection of malicious scripts through user-supplied input that is improperly sanitized before being rendered in web pages. The vulnerability exists in the like button functionality where injected script payloads execute when other users view pages containing the compromised button.

MitigationUpdate the LikeBtn Like Button Rating plugin to the latest version which should include proper input sanitization/validation. If no update is available, implement output encoding and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Like Button RatingWordPress extension
Affected:< 2.6.54

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 LikeBtn plugin is installed
    Check for the presence of the likebtn-like-button-rating directory in wp-content/plugins/ or look for 'LikeBtn Like Button Rating' in WordPress admin under Plugins
    Affected if Plugin is not installed or not present in the WordPress installation
  2. Check installed plugin version
    Open the main plugin file (likebtn.php) in wp-content/plugins/likebtn-like-button-rating/ and locate the Version header in the plugin comment block, or view the plugin in WordPress admin Plugins page
    Affected if Version number is less than 2.6.54 (e.g., 2.6.53, 2.6.5, 2.6.0, etc.)
  3. Identify like button shortcode or widget usage
    Search your WordPress posts, pages, and widgets for [likebtn] shortcode usage or LikeBtn widget instances that accept user-supplied parameters
    Affected if The like button functionality with user-controllable parameters is actively used on the site
  4. Inspect rendered HTML for lack of sanitization
    View a page containing a like button in a browser, right-click and Inspect Element, then check if button parameters or content are reflected without proper encoding (look for unescaped HTML attributes or content)
    Affected if User-supplied values in the like button appear as raw text in HTML without HTML entity encoding

You are affected if the LikeBtn Like Button Rating plugin is installed with a version lower than 2.6.54 and the like button with user-supplied input is being displayed on pages.

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
Upgrade available Upgrade to 2.6.54 or later
Fixed in 2.6.54
Interim mitigation

Update the LikeBtn Like Button Rating plugin to the latest version which should include proper input sanitization/validation. If no update is available, implement output encoding and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

Like Button Rating version 2.6.54

  1. Create a full backup of your WordPress site before making any changes
  2. Update the Like Button Rating plugin to version 2.6.54 through the WordPress admin dashboard (Plugins > Installed Plugins > Like Button Rating > Update now) or via wp-cli: wp update plugin likebtn-like-button
  3. After updating, verify the installed version is 2.6.54 by checking the Plugins page in WordPress admin
  4. Clear any caching layers (page cache, CDN cache) to ensure the fixed code is served

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

Fix this in Like Button Rating Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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