Extended Post Status · Security record
Is Extended Post Status safe?
No known vulnerability affects the current version (1.1.1). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 2, 2023.
Checked 2 days ago against the WPVulnerability database, for version 1.1.1.
How it’s looked after
- Last release
- Sep 1, 2026 (2 months ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Active installs
- 1K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Extended Post Status
Newest first, with any that affect the current version at the top.
Fixed in 1.0.20 · CVE-2023-32094 · Jun 2, 2023 · Wordfence
Questions about Extended Post Status’s security
Is Extended Post Status safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Extended Post Status updated: most attacks target sites that haven’t updated.
Does Extended Post Status have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Extended Post Status up to date.
Is Extended Post Status still maintained?
Yes. Its last release was 2 months ago. No support threads were opened in the last two months.
Is Extended Post Status compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
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.