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