No Page Comment · Security record
Is No Page Comment safe?
No known vulnerability affects the current version (1.3.1). 2 issues were found in earlier versions and fixed, the latest disclosed on Sep 21, 2022.
Checked 4 days ago against the WPVulnerability database, for version 1.3.1.
How it’s looked after
- Last release
- Nov 17, 2025 (11 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Active installs
- 10K+
2 known vulnerabilities
- 2 not rated
None affects the current version.
Every known vulnerability in No Page Comment
Newest first, with any that affect the current version at the top.
Fixed in 1.2 · Sep 21, 2022 · Wordfence
Fixed in 1.2 · Sep 20, 2022 · Wordfence
Questions about No Page Comment’s security
Is No Page Comment safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep No Page Comment updated: most attacks target sites that haven’t updated.
Does No Page Comment have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep No Page Comment up to date.
Is No Page Comment still maintained?
Its last release was 11 months ago. No support threads were opened in the last two months.
Is No Page Comment compatible with the latest WordPress?
No Page Comment’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.