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