Get Started
CVE July 21, 2026 5 min read

Motors Theme CVE-2025-4322: Unauthenticated Admin Account Takeover on 22,000+ WordPress Sites (CVSS 9.8)

CVE-2025-4322 is a critical flaw in the premium Motors WordPress theme that let unauthenticated attackers reset any user's password, including administrators, and hijack the site. It affects versions up to 5.6.67 and is fixed in 5.6.68. With active exploitation across 22,000+ sites, updating immediately is essential.

In May 2025, security researchers disclosed a critical flaw in Motors, a popular premium WordPress theme built by StylemixThemes for car dealerships, rental businesses, and automotive listings. Tracked as CVE-2025-4322, the vulnerability let unauthenticated attackers reset any user’s password — including an administrator’s — and take over the account. With more than 22,000 sites running the theme, and mass exploitation observed within weeks of disclosure, this is one of the most consequential WordPress theme vulnerabilities of the year. If your site runs Motors, this is a drop-everything-and-patch situation.

CVE at a Glance

  • CVE ID: CVE-2025-4322
  • Affected software: Motors theme for WordPress (by StylemixThemes)
  • CVSS 3.1 score: 9.8 (Critical)
  • Vulnerability type: Unauthenticated Privilege Escalation / Account Takeover (CWE-620: Unverified Password Change)
  • Affected versions: All versions up to and including 5.6.67
  • Patched version: 5.6.68
  • Authentication required: None
  • Status: Actively exploited in the wild

The flaw was reported through Wordfence’s bug bounty program by a researcher known as “Foxyyy.” StylemixThemes released the fix in version 5.6.68 on May 14, 2025, and the vulnerability was publicly disclosed on May 19. Attackers wasted no time: the first exploitation attempts appeared on May 20, and mass exploitation began around June 7. Tens of thousands of attack attempts have been recorded since.

How the Vulnerability Works

Motors ships with a front-end “Login Register” element that lets visitors sign in, register, and recover a forgotten password without going through the standard WordPress login screen. The password recovery flow is where things went wrong.

When a legitimate user requests a password reset, the theme generates a secret value (a “hash check”) that is supposed to prove the request came from the real account owner before any new password is saved. The problem is that Motors did not properly validate that secret against the specific user being modified. In practice, the password-update endpoint accepted a request that supplied a target user_id, an attacker-controlled hash value, and a brand-new password — and then updated the password without ever confirming the requester was actually authorized to do so.

Because WordPress administrator accounts commonly sit at a low, predictable user ID (the first admin is often user ID 1), an attacker doesn’t need to know a username, an email address, or the current password. They simply point the vulnerable request at an administrator’s user ID, supply a password of their choosing, and the theme rewrites it. To pull this off, an attacker needs nothing more than the URL of a vulnerable site and the ability to send an HTTP request — no login, no user interaction, no social engineering.

Real-World Impact

An unverified password change that reaches administrator accounts is effectively a full site takeover. Once an attacker resets an admin password and logs in, they hold the keys to everything WordPress can do:

  • Install malicious plugins or theme code to establish a persistent backdoor
  • Create additional hidden administrator accounts so they retain access even after the original password is restored
  • Inject spam, SEO redirects, or malware that infects visitors
  • Steal customer data, order records, and any personal information stored in the site database
  • Deface the site, take it offline, or hold it for ransom

A common tell of successful exploitation reported in the wild is the sudden appearance of an unfamiliar administrator account and the locking-out of the real site owner, whose password no longer works. Because Motors is used heavily by dealerships and rental businesses handling customer inquiries and payment-adjacent data, a compromise can carry real regulatory and reputational consequences, not just downtime.

How to Check If You’re Affected

You are potentially exposed if your site uses the Motors theme (or any child theme built on it) at version 5.6.67 or earlier. To confirm:

  • In your WordPress dashboard, go to Appearance > Themes and open the active theme’s details to read the version number.
  • Alternatively, check the theme’s style.css header at wp-content/themes/motors/style.css and look for the Version: line.
  • If you run a child theme, verify the version of the parent Motors theme, since that is where the vulnerable code lives.

If the version is 5.6.67 or lower, assume you are vulnerable. Given active exploitation, also treat any recently patched site as potentially already compromised and review it for signs of intrusion.

How to Fix It

The essential step is simple: update the Motors theme to version 5.6.68 or later immediately. Because Motors is a premium theme, updates typically arrive through the theme’s own updater or via your ThemeForest/StylemixThemes account rather than the WordPress.org repository. If automatic updates are not configured, download the latest release and update manually.

Because this flaw has been exploited at scale, patching alone is not enough. Take these additional steps to confirm you haven’t already been breached and to harden the site:

  • Audit your user accounts. Go to Users > All Users and delete any administrator you don’t recognize.
  • Reset all administrator passwords and, ideally, force a password reset for all users after updating.
  • Enable two-factor authentication for every administrator so a stolen or reset password alone can’t grant access.
  • Review recent changes — newly installed plugins, modified core files, unexpected scheduled tasks (cron jobs), and admin activity logs.
  • Rotate secrets such as your WordPress security keys (salts in wp-config.php) to invalidate any hijacked sessions.
  • Run a full malware scan with a reputable security plugin, and if you find evidence of compromise, restore from a known-clean backup.

A web application firewall (WAF) can also block exploit attempts targeting the vulnerable endpoint, buying time if you can’t patch instantly — but it should be treated as a safety net, not a replacement for updating.

Takeaway

CVE-2025-4322 is a textbook reminder that themes deserve the same security attention as plugins. A single missing identity check in a password-reset routine turned a popular commercial theme into a remote takeover tool for tens of thousands of sites. The defenses are the same ones that protect against most WordPress incidents: keep everything updated the moment patches ship, minimize the number of administrator accounts, require two-factor authentication, monitor for unexpected users and file changes, and keep clean, tested backups. Premium doesn’t mean invulnerable — and on WordPress, the gap between disclosure and mass exploitation is now measured in days.

Related Articles