Inactive Logout <= 3.2.2 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.2.3
- Affected Plugin
- Inactive Logout
- Affected Version
< 3.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE pending
At a glance
This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Inactive Logout WordPress plugin, affecting versions < 3.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed September 2023.
Vulnerability Overview
The Inactive Logout plugin for WordPress is vulnerable to Cross-Site Request Forgery due to a missing nonce check on the ina_reset_adv_settings() function in versions up to, and including, 3.2.2. This makes it possible for unauthenticated attackers to reset the plugin's settings 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.
CWE-352: Cross-Site Request Forgery (CSRF)
Inactive Logout < 3.2.3 carries this weakness at ina_reset_adv_settings(), and reaching it 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 Inactive Logout the fix is 3.2.3: builds < 3.2.3 are affected, anything from 3.2.3 onward is not.
Remediation
Update to version 3.2.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Inactive Logout: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Inactive Logout 3.2.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C