CVE-2024-39623

ListingPro <= 2.9.4 - Cross-Site Request Forgery to Account Takeover

2024-07-22 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 2.9.5
Affected Version
<= 2.9.4
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-39623
View all ListingPro - WordPress Directory & Listing Theme vulnerabilities

At a glance

CVE-2024-39623 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the ListingPro - WordPress Directory & Listing Theme WordPress theme, affecting versions <= 2.9.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.9.5; sites on affected versions should update now. Disclosed July 2024, reported by Rafie Muhammad.

Vulnerability Overview

The ListingPro theme for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.9.4. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to takeover user accounts 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in ListingPro - WordPress Directory & Listing Theme <= 2.9.4 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 ListingPro - WordPress Directory & Listing Theme the fix is 2.9.5: builds <= 2.9.4 are affected, anything from 2.9.5 onward is not.

Remediation

Update to version 2.9.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to ListingPro - WordPress Directory & Listing Theme: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ListingPro - WordPress Directory & Listing Theme 2.9.5 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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