Exertio Framework <= 1.3.1 - Unauthenticated Arbitrary User Password Update
Strategic Overview
- Status
- Patched in 1.3.2
- Affected Plugin
- Exertio Framework
- Affected Version
<= 1.3.1- CVSS
- 8.1High
- Weakness type
- CWE-620 · Unverified Password Change
- CVE
CVE-2024-13373
At a glance
CVE-2024-13373 is a high-severity Unverified Password Change vulnerability in the Exertio Framework WordPress plugin, affecting versions <= 1.3.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3.2; sites on affected versions should update now. Disclosed February 2025, reported by Foxyyy.
Vulnerability Overview
The Exertio Framework plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.3.1. This is due to the plugin not properly validating a user's identity prior to updating their password through the fl_forgot_pass_new() function. 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, 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
Exertio Framework <= 1.3.1 carries this weakness at fl_forgot_pass_new(), 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 Exertio Framework the fix is 1.3.2: builds <= 1.3.1 are affected, anything from 1.3.2 onward is not.
Remediation
Update to version 1.3.2, 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: Exertio Framework 1.3.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Exertio Framework
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C