HTTP Auth · Security record
Is HTTP Auth safe?
No known vulnerability affects the current version (1.0.1). 1 issue was found in earlier versions and fixed, the latest disclosed on Jul 26, 2023.
Checked 2 days ago against the WPVulnerability database, for version 1.0.1.
How it’s looked after
- Last release
- Jul 22, 2025 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Active installs
- 6K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in HTTP Auth
Newest first, with any that affect the current version at the top.
Fixed in 1.0.0 · CVE-2023-27435 · Jul 26, 2023 · Wordfence
Questions about HTTP Auth’s security
Is HTTP Auth safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep HTTP Auth updated: most attacks target sites that haven’t updated.
Does HTTP Auth have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep HTTP Auth up to date.
Is HTTP Auth still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is HTTP Auth compatible with the latest WordPress?
HTTP Auth’s readme says it’s tested up to WordPress 6.8.12, 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.