CVE-2026-0909

WP ULike <= 4.8.3.1 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Log Deletion via 'id' Parameter

2026-02-02 14:51
Pouria Shahba (p0or1ya)

Strategic Overview

Status
Patched in 5.0.0
Affected Plugin
WP ULike – Like Buttons, Voting & Engagement Analytics
Affected Version
<= 4.8.3.1
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-0909
View all WP ULike – Like Buttons, Voting & Engagement Analytics vulnerabilities

At a glance

CVE-2026-0909 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP ULike WordPress plugin, affecting versions <= 4.8.3.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.0.0; sites on affected versions should update now. Disclosed February 2026, reported by Pouria Shahba (p0or1ya).

Vulnerability Overview

The WP ULike plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.8.3.1. This is due to the `wp_ulike_delete_history_api` AJAX action not verifying that the log entry being deleted belongs to the current user. This makes it possible for authenticated attackers, with Subscriber-level access and above (granted the 'stats' capability is assigned to their role), to delete arbitrary log entries belonging to other users via the 'id' parameter.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

WP ULike <= 4.8.3.1 carries this weakness at stats, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP ULike the fix is 5.0.0: builds <= 4.8.3.1 are affected, anything from 5.0.0 onward is not.

Remediation

Update to version 5.0.0, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP ULike 5.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0909https://www.wordfence.com/threat-intel/vulnerabilities/id/bee2e520-46cc-4b54-9849-fafb9b37ba19https://nvd.nist.gov/vuln/detail/CVE-2026-0909

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C