JWT Auth · Security record
Is JWT Auth safe?
No known vulnerability affects the current version (3.0.2). 1 issue was found in earlier versions and fixed, the latest disclosed on Mar 29, 2022.
Checked 4 days ago against the WPVulnerability database, for version 3.0.2.
How it’s looked after
- Last release
- May 7, 2024 (2 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.5.13 (current: 7.1)
- Active installs
- 6K+
1 known vulnerability
- 1 critical
None affects the current version.
Every known vulnerability in JWT Auth
Newest first, with any that affect the current version at the top.
- critical
Algorithm Confusion
Fixed in 2.1.1 · CVE-2021-46743 · Mar 29, 2022 · Wordfence
Questions about JWT Auth’s security
Is JWT Auth safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep JWT Auth updated: most attacks target sites that haven’t updated.
Does JWT Auth have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep JWT Auth up to date.
Is JWT Auth still maintained?
Its last release was 2 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is JWT Auth compatible with the latest WordPress?
JWT Auth’s readme says it’s tested up to WordPress 6.5.13, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.