CVE-2026-2358: WP ULike – Like & Dislike Buttons for Engagement and Feedback · Cross-site Scripting
Affects WP ULike – Like & Dislike Buttons for Engagement and FeedbackSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| alimirWP ULike – Like & Dislike Buttons for Engagement and Feedback | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict Contributor-level access to trusted users only and consider disabling or removing the WP ULike plugin if feasible. Monitor for updates from the plugin vendor or WordPress security advisories to apply any forthcoming patches promptly.
Description
The WP ULike plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `[wp_ulike_likers_box]` shortcode `template` attribute in all versions up to, and including, 5.0.1. This is due to the use of `html_entity_decode()` on shortcode attributes without subsequent output sanitization, which effectively bypasses WordPress's `wp_kses_post()` content filtering. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The post must have at least one like for the XSS to render.
References
- wordfence.com/threat-intel/vulnerabilities/id/74a7db23-f91c-452b-bc24-58fda69caf17?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-ulike/trunk/includes/hooks/shortcodes.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-ulike/trunk/includes/functions/utilities.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-ulike/trunk/includes/functions/utilities.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-ulike/trunk/includes/functions/general.php (opens in a new tab)
- github.com/Alimir/wp-ulike/commit/3dcce696ea251b3733448332cc167e03b2a17c12 (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3475381%40wp-ulike%2Ftrunk&old=3457255%40wp-ulike%2Ftrunk&sfp_email=&sfph_mail= (opens in a new tab)