Skip to main content
CVE-2026-116552VulnerabilityPublished

The Like Button Rating ♥ LikeBtn plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116552· Medium 4.7

Not known to be exploited · CVSS 4.7 Medium.

Data as of 30 Oct 2026, 20:03 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 default 'Be GDPR compliant' option in the plugin, which hashes stored IP addresses, mitigates the vulnerability by neutralizing the payload. Administrators should ensure this option remains enabled. Until an official fix is released, avoid disabling this GDPR compliance feature and restrict administrator actions that could trigger the vulnerability.

Description

The Like Button Rating ♥ LikeBtn plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the HTTP_CLIENT_IP header parameter. This affects all versions up to and including 2.6.64. The vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires the site administrator to have disabled the default 'Be GDPR compliant' option, which normally hashes IP addresses to prevent payload execution. Additionally, an administrator action is necessary to trigger the vulnerability, as attackers cannot exploit it independently.

References

Community reviews

Loading reviews…