CVE-2024-12860

CarSpot – Dealership Wordpress Classified Theme <= 2.4.3 - Unauthenticated Arbitrary Password Reset/Account Takeover

2025-02-17 20:04
Lucio Sá

Strategic Overview

Status
Patched in 2.4.4
Affected Version
<= 2.4.3
CVSS
9.8Critical
Weakness type
CWE-620 · Unverified Password Change
CVE
CVE-2024-12860
View all CarSpot – Dealership Wordpress Classified Theme vulnerabilities

At a glance

CVE-2024-12860 is a critical-severity Unverified Password Change vulnerability in the CarSpot WordPress theme, affecting versions <= 2.4.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.4; sites on affected versions should update now. Disclosed February 2025, reported by Lucio Sá.

Vulnerability Overview

The CarSpot – Dealership Wordpress Classified Theme theme for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 2.4.3. This is due to the plugin not properly validating a token prior to updating a user's password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-620: Unverified Password Change

Reaching this weakness in CarSpot <= 2.4.3 takes no account at all. Unverified password change means the password-update path does not require proof that the requester is the account owner.

An attacker who can reach the endpoint takes over the account outright, and the legitimate owner is locked out of it. For CarSpot the fix is 2.4.4: builds <= 2.4.3 are affected, anything from 2.4.4 onward is not.

Remediation

Update to version 2.4.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: CarSpot 2.4.4 closes this, and updating the theme is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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