Skip to main content
VulnerabilityPublished

CVE-2026-116552: Like Button Rating ♥ LikeBtn (WordPress plugin) · Cross-site Scripting

Affects Like Button Rating ♥ LikeBtn (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.7 Medium.

Data as of 30 Oct 2026, 20:38 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.14.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
likebtnLike Button Rating ♥ LikeBtnAffected
  • <=2.6.64
Fixed in–

AI-suggested

The vulnerability is mitigated if the default 'Be GDPR compliant' option is enabled, as it hashes stored IP addresses and neutralizes the payload. Site administrators should ensure this option remains enabled. Additionally, administrators should exercise caution with actions that could trigger the vulnerability. Monitor vendor advisories for any forthcoming patches or updates.

Description

The Like Button Rating ♥ LikeBtn plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HTTP_CLIENT_IP (Client-IP header)' parameter in all versions up to, and including, 2.6.64 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires the site administrator to have disabled the default 'Be GDPR compliant' option, which would otherwise hash stored IP values and neutralize the payload. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

References

Community reviews

Loading reviews…