Next Page, Not Next Post · Security record
Is Next Page, Not Next Post safe?
One known vulnerability affects the current version (0.3.0), and it has no fix yet.
Checked 3 days ago against the WPVulnerability database, for version 0.3.0.
How it’s looked after
- Last release
- Sep 4, 2014 (12 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 4.0.38 (current: 7.1)
- Active installs
- 1K+
1 known vulnerability
- 1 medium
1 affects the current version. 1 has no fix yet.
Every known vulnerability in Next Page, Not Next Post
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2025-62943 · Oct 10, 2025 · Wordfence
Questions about Next Page, Not Next Post’s security
Is Next Page, Not Next Post safe to use?
Yes: 1 known vulnerability affects version 0.3.0, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Next Page, Not Next Post have known security vulnerabilities?
Yes: 1 known vulnerability affects version 0.3.0, according to WPVulnerability’s database.
Is Next Page, Not Next Post still maintained?
Its last release was 12 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is Next Page, Not Next Post compatible with the latest WordPress?
Next Page, Not Next Post’s readme says it’s tested up to WordPress 4.0.38, 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.