CVE-2024-9649

WP ULike <= 4.7.4 - Cross-Site Request Forgery to Statistic Deletion

2024-10-15 00:00
Bilal Chawich (Duke)

Strategic Overview

Status
Patched in 4.7.5
Affected Plugin
WP ULike – Like Buttons, Voting & Engagement Analytics
Affected Version
<= 4.7.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-9649
View all WP ULike – Like Buttons, Voting & Engagement Analytics vulnerabilities

At a glance

CVE-2024-9649 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP ULike WordPress plugin, affecting versions <= 4.7.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.7.5; sites on affected versions should update now. Disclosed October 2024, reported by Bilal Chawich (Duke).

Vulnerability Overview

The WP ULike – The Ultimate Engagement Toolkit for Websites plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.7.4. This is due to missing or incorrect nonce validation on the wp_ulike_delete_history_api() function. This makes it possible for unauthenticated attackers to delete engagements via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

WP ULike <= 4.7.4 carries this weakness at wp_ulike_delete_history_api(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP ULike the fix is 4.7.5: builds <= 4.7.4 are affected, anything from 4.7.5 onward is not.

Remediation

Update to version 4.7.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP ULike: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP ULike 4.7.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-9649https://www.wordfence.com/threat-intel/vulnerabilities/id/3fcb35f8-ed88-4440-8cdf-95c1f0028253https://nvd.nist.gov/vuln/detail/CVE-2024-9649

Related records

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