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