LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2358 affects the WP ULike WordPress plugin through version 5.0.1. A logged-in user with Contributor or higher access can store script content in a shortcode attribute. The script runs when someone views the affected page, but the post must have at least one like for rendering.

Executive priority

Treat as a medium-priority website integrity risk. Prioritize public WordPress sites with multiple content contributors or weak account governance. The main business concern is unauthorized script execution affecting visitors or administrators who view injected pages.

Technical view

The issue is stored XSS in the [wp_ulike_likers_box] shortcode template attribute. The CVE states html_entity_decode() is applied to shortcode attributes without later output sanitization, bypassing WordPress wp_kses_post() filtering. CVSS is 6.4, PR:L, AC:L, scope changed, with low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites running WP ULike versions up to and including 5.0.1, where untrusted Contributor-level users can create or edit posts using shortcodes.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked as KEV. Exploitation requires authenticated Contributor-level or higher access and a page condition where the affected post has at least one like.

Researcher notes

The vulnerable path centers on shortcode attribute handling and output rendering. The CVE notes the XSS only renders when the post has at least one like. Source evidence includes Wordfence, WordPress Trac code references, a GitHub commit, and a WordPress plugin changeset.

Mitigation direction

  • Update WP ULike beyond affected versions when vendor guidance confirms the fixed release.
  • Review the linked vendor commit and WordPress plugin changeset for remediation details.
  • Restrict Contributor access to trusted users until remediation is complete.
  • Audit posts using the wp_ulike_likers_box shortcode, especially with template attributes.

Validation and detection

  • Inventory WordPress sites using WP ULike and identify plugin versions.
  • Flag installations running WP ULike 5.0.1 or earlier.
  • Review Contributor-authored posts for wp_ulike_likers_box shortcode usage.
  • Confirm remediation by checking vendor release notes or the referenced code changes.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2358 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-2358Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
alimirWP ULike – Like & Dislike Buttons for Engagement and Feedback0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.