CVE-2024-9661

WP All Import Pro <= 4.9.7 - Cross-Site Request Forgery to Imported Content Deletion

2025-02-07 03:06
Francesco Carlucci

Strategic Overview

Status
Patched in 4.9.8
Affected Plugin
WP All Import Pro
Affected Version
<= 4.9.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-9661
View all WP All Import Pro vulnerabilities

At a glance

CVE-2024-9661 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP All Import Pro WordPress plugin, affecting versions <= 4.9.7. 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.9.8; sites on affected versions should update now. Disclosed February 2025, reported by Francesco Carlucci.

Vulnerability Overview

The WP All Import Pro plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.9.7. This is due to missing nonce validation on the delete_and_edit function. This makes it possible for unauthenticated attackers to delete imported content (posts, comments, users, etc.) 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)

Reaching this weakness in WP All Import Pro <= 4.9.7 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 All Import Pro the fix is 4.9.8: builds <= 4.9.7 are affected, anything from 4.9.8 onward is not.

Remediation

Update to version 4.9.8, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-9661https://www.wordfence.com/threat-intel/vulnerabilities/id/b5f8659a-fb3f-4df3-85a6-979751627a9chttps://nvd.nist.gov/vuln/detail/CVE-2024-9661

Related records

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