Strategic Overview
- Status
- Patched in 3.2.1
- Affected Plugin
- Simple JWT Login – Allows you to use JWT on REST endpoints.
- Affected Version
< 3.2.1- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-24804
At a glance
CVE-2021-24804 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Simple JWT Login WordPress plugin, affecting versions < 3.2.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.1; sites on affected versions should update now. Disclosed October 2021, reported by apple502j.
Vulnerability Overview
The Simple JWT Login WordPress plugin before 3.2.1 does not have nonce checks when saving its settings, allowing attackers to make a logged in admin changed them. Settings such as HMAC verification secret, account registering and default user roles can be updated, which could result in site takeover.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Simple JWT Login < 3.2.1 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 Simple JWT Login the fix is 3.2.1: builds < 3.2.1 are affected, anything from 3.2.1 onward is not.
Remediation
Update to version 3.2.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Simple JWT Login: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Simple JWT Login 3.2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Simple JWT Login – Allows you to use JWT on REST endpoints.
- 8.8CVE-2026-14262: Simple JWT Login Authentication Bypass
CVE-2026-14262 - 7.5CVE-2021-24998: Simple JWT Login <= 3.2.1 Insecure Password Creation
CVE-2021-24998 - 7.3CVE-2026-19714: Simple JWT Login Privilege Escalation
CVE-2026-19714 - 6.4CVE-2025-58648: Simple JWT Login <= 3.6.4 Stored Cross-Site Scripting
CVE-2025-58648
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C