LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

WP ULike for WordPress can let certain logged-in users delete other users’ plugin history records. This is not a site takeover issue, but it can damage engagement records and auditability. Sites with public registration or many low-privilege users should prioritize review.

Executive priority

Handle in the normal vulnerability queue, faster for sites with public registration or community users. The business concern is tampering with engagement/history records rather than full compromise.

Technical view

CVE-2026-0909 is an IDOR/CWE-639 in WP ULike through 4.8.3.1. The wp_ulike_delete_history_api AJAX action did not verify that the requested log entry belonged to the current user, allowing arbitrary log deletion through the id parameter by users with Subscriber-level access and the stats capability.

Likely exposure

Exposure is limited to WordPress sites using WP ULike versions up to 4.8.3.1 where authenticated users have the stats capability. Risk is higher when untrusted users can register or receive Subscriber-level accounts.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. Exploitation requires access conditions described by Wordfence/CVE sources. The impact is integrity loss of WP ULike log/history data, not code execution.

Researcher notes

Sources describe authenticated Subscriber+ exploitation with stats capability, while the provided CVSS vector lists PR:N. Treat that as an evidence inconsistency. A WordPress Trac changeset is referenced, but the bundle does not name a fixed release version.

Mitigation direction

  • Inventory WordPress sites using the WP ULike plugin.
  • Check installed WP ULike versions for 4.8.3.1 or earlier.
  • Review vendor/plugin guidance for a fixed release before upgrading.
  • Remove the stats capability from untrusted low-privilege roles.
  • Limit site registration or access where untrusted users can log in.

Validation and detection

  • Confirm whether WP ULike is installed and active.
  • Record the installed plugin version on each site.
  • Review roles assigned the stats capability.
  • Check whether untrusted Subscriber-level users exist.
  • Verify vendor code includes ownership checks for delete-history requests.
Prepared
Confidence
medium
Sources
6

Public sources used

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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-0909 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
5Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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

Source materials

Affected products

Products and packages named in the record

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

CWE details

CWE-639

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs