CVE-2025-32259

WP ULike <= 4.7.9.1 - Missing Authorization to Unauthenticated Content Spoofing

2025-04-04 00:00
Robert DeVore

Strategic Overview

Status
Patched in 4.7.10
Affected Plugin
WP ULike – Like Buttons, Voting & Engagement Analytics
Affected Version
<= 4.7.9.1
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-32259
View all WP ULike – Like Buttons, Voting & Engagement Analytics vulnerabilities

At a glance

CVE-2025-32259 is a medium-severity Missing Authorization vulnerability in the WP ULike WordPress plugin, affecting versions <= 4.7.9.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 4.7.10; sites on affected versions should update now. Disclosed April 2025, reported by Robert DeVore.

Vulnerability Overview

The WP ULike – All-in-One Engagement Toolkit plugin for WordPress is vulnerable to content spoofing due to a missing capability check on a function in all versions up to, and including, 4.7.9.1. This makes it possible for unauthenticated attackers to spoof content.

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-862: Missing Authorization

Reaching this weakness in WP ULike <= 4.7.9.1 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP ULike the fix is 4.7.10: builds <= 4.7.9.1 are affected, anything from 4.7.10 onward is not.

Remediation

Update to version 4.7.10, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP ULike 4.7.10 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-32259https://www.wordfence.com/threat-intel/vulnerabilities/id/f72a8b6b-2eef-4245-b215-5ae6fa31e650https://nvd.nist.gov/vuln/detail/CVE-2025-32259

Related records

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