CVE-2026-2358 MEDIUM

CVE-2026-2358: WP ULike <= 5.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attribute

Vendor Alimir
Product WP ULike – Like & Dislike Buttons for Engagement and Feedback
Weakness CWE-79 · XSS
Published March 11, 2026
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

WP ULike versions up to 5.0.1 contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts. The vulnerability has changed scope, meaning injected code can affect other users and site functionality beyond the plugin itself. An attacker with low-level WordPress access can craft malicious input that executes in other users' browsers.

What an attacker can do

03Attacker Capabilities

Inject JavaScript that runs in other users' browsers and affects site functionality.

Potential impact on your site

04Site Impact

Authenticated attackers can steal session cookies, deface content, or redirect users to malicious sites.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level WordPress user account (e.g., subscriber or contributor).

Key dates

06Disclosure timeline

March 11, 2026 CVE published
April 8, 2026 Record updated