IMITHEMES Listing <= 3.3 - Unauthenticated Privilege Escalation via Unverified Password Reset
Strategic Overview
- Status
- Patched in 3.4
- Affected Plugin
- IMITHEMES Listing
- Affected Version
<= 3.3- CVSS
- 9.8Critical
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2025-2253
At a glance
CVE-2025-2253 is a critical-severity Unverified Password Change vulnerability in the IMITHEMES Listing WordPress plugin, affecting versions <= 3.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 3.4; sites on affected versions should update now. Disclosed May 2025, reported by Alyudin Nafiie.
Vulnerability Overview
The IMITHEMES Listing plugin is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.3. This is due to the plugin not properly validating a verification code value prior to updating their password through the imic_reset_password_init() function. This makes it possible for unauthenticated attackers to change any user's passwords, including administrators if the users email is known.
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
IMITHEMES Listing <= 3.3 carries this weakness at imic_reset_password_init(), and reaching it 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 IMITHEMES Listing the fix is 3.4: builds <= 3.3 are affected, anything from 3.4 onward is not.
Remediation
Update to version 3.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: IMITHEMES Listing 3.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C