VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-0909Published · Updated

Action summary

Affected: ≤4.8.3.1Update to 5.0.0 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

WP ULike – Like Buttons, Voting & Engagement Analytics wp-ulike

  1. Affected≤ 4.8.3.1
  2. Patched in5.0.0

Update to 5.0.0 or newer.

You are affected if you run ≤ 4.8.3.1. Version 5.0.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WP ULike – Like Buttons, Voting & Engagement Analytics.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 5.0.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WP ULike – Like Buttons, Voting & Engagement Analytics to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Pouria Shahba (p0or1ya).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WP ULike – Like Buttons, Voting & Engagement Analytics

All 17
More vulnerabilities in WP ULike – Like Buttons, Voting & Engagement Analytics
SeverityVulnerabilityCVEPublished
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attribute
≤5.0.1Update to 5.0.2
CVE-2026-2358
Medium5.3Missing Authorization to Unauthenticated Content Spoofing
≤4.7.9.1Update to 4.7.10
CVE-2025-32259
Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤4.7.5Update to 4.7.6
CVE-2024-12770
Medium4.4Authenticated (Administrator+) Stored Cross-Site Scripting
≤4.7.6Update to 4.7.7
CVE-2025-22738
Medium4.3Cross-Site Request Forgery to Statistic Deletion
≤4.7.4Update to 4.7.5
CVE-2024-9649

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?