sales@hackhalt.com

Home / Threats / CVE-2024-9649

Wp Ulike - Cross-Site Request Forgery (CSRF) (CVE-2024-9649)

CVE-2024-9649

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.

CVE-2024-9649

MEDIUM CVSS 4.3 Published 2024-10-16 Updated 2026-06-17
AI Risk Elevated (72/100) Active Exploit: Likely Published Exploit: Public exploit references found Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Affected Components 1
Reference Links 3
AI Risk Engine Elevated (72/100)
Exploitability High
Active Exploitation Likely
Published Exploit Status Public exploit references found

Threat Timeline

  1. 2024-10-16 CVE published and first recorded in the threat feed.
  2. 2026-06-17 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 166 days ago

AI enriched 166 days ago (2026-04-09 09:58 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 4.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on published exploit references, remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: published exploit references, remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Wp Ulike PLUGIN · wp-ulike Affected: < 4.7.5 Fixed in: 4.7.5

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Wp Ulike to 4.7.5 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Wp Ulike, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Wp Ulike. Versions below 4.7.5 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Wp Ulike to version 4.7.5 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Cross-Site Request Forgery (CSRF) flaw. An attacker who exploits it can make a logged-in administrator perform an action just by visiting a page.