CVE-2024-49275

IdeaPush <= 8.69 - Cross-Site Request Forgery

2024-10-14 00:00
theviper17y

Strategic Overview

Status
Patched in 8.71
Affected Plugin
IdeaPush
Affected Version
<= 8.69
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-49275
View all IdeaPush vulnerabilities

At a glance

CVE-2024-49275 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the IdeaPush WordPress plugin, affecting versions <= 8.69. 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 8.71; sites on affected versions should update now. Disclosed October 2024, reported by theviper17y.

Vulnerability Overview

The IdeaPush plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.69. This is due to missing or incorrect nonce validation on the idea_push_update_user_profile() function. This makes it possible for unauthenticated attackers to update user profiles 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)

IdeaPush <= 8.69 carries this weakness at idea_push_update_user_profile(), 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 IdeaPush the fix is 8.71: builds <= 8.69 are affected, anything from 8.71 onward is not.

Remediation

Update to version 8.71, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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