dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-0909

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP ULike plugin for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability in the wp_ulike_delete_history_api AJAX action. The function fails to verify that the log entry being deleted (via the 'id' parameter) belongs to the authenticated user making the request, allowing any authenticated user with 'stats' capability to delete arbitrary log entries from other users.

MitigationUpdate WP ULike to version 4.8.4 or later. Alternatively, modify the wp_ulike_delete_history_api function to verify that the log entry's user_id matches the current authenticated user before allowing deletion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP ULike plugin is installed
    Navigate to WordPress admin > Plugins and confirm WP ULike is active, or check the /wp-content/plugins/ directory for the wp-ulike folder
    Affected if WP ULike plugin is not installed or not active
  2. Check installed WP ULike version
    In WordPress admin > Plugins, find WP ULike and view the version number, or check the version in the plugin's main PHP file header
    Affected if Version is present and less than 4.8.4 (the version where the vulnerability was fixed)
  3. Confirm user roles with stats capability exist
    Check WordPress user roles and capabilities. The 'stats' capability is typically assigned to administrator roles. Review user accounts to see which users have this capability.
    Affected if Any authenticated user account with 'stats' capability exists on the site
  4. Verify AJAX action endpoint is accessible
    Check if the wp_ulike_delete_history_api AJAX action is registered and accessible. This can be confirmed by examining the plugin's AJAX handlers or by testing the endpoint at /wp-admin/admin-ajax.php?action=wp_ulike_delete_history_api
    Affected if The AJAX endpoint responds and accepts the 'id' parameter without user ownership validation

You are affected if WP ULike version is below 4.8.4 AND any authenticated user with 'stats' capability exists on your WordPress site, as such a user could exploit the IDOR to delete arbitrary log entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP ULike to version 4.8.4 or later. Alternatively, modify the wp_ulike_delete_history_api function to verify that the log entry's user_id matches the current authenticated user before allowing deletion.

Recommended fix Moderate confidence

WP ULike version 4.8.4 or latest stable release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP ULike plugin
  4. Check if an update is available and update to the latest version (4.8.4 or higher)
  5. Alternatively, navigate to Dashboard > Updates to check for available updates
  6. If no update appears, manually download the latest version from the WordPress plugin repository and reinstall
Caveat No known breaking changes; this is a security patch update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0909 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data