Plugin Check (PCP) · Security record
Is Plugin Check (PCP) safe?
No known vulnerability affects the current version (2.2.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Dec 6, 2024.
Checked 2 days ago against the WPVulnerability database, for version 2.2.0.
How it’s looked after
- Last release
- Nov 6, 2026 (2 days ago)
- Releases in the last year
- 6
- Tested up to
- WordPress 7.0.8
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 10K+
1 known vulnerability
- 1 not rated
None affects the current version.
Every known vulnerability in Plugin Check (PCP)
Newest first, with any that affect the current version at the top.
Fixed in 1.3.1 · Dec 6, 2024 · Patchstack
Questions about Plugin Check (PCP)’s security
Is Plugin Check (PCP) safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Plugin Check (PCP) updated: most attacks target sites that haven’t updated.
Does Plugin Check (PCP) have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Plugin Check (PCP) up to date.
Is Plugin Check (PCP) still maintained?
Yes. Its last release was 2 days ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Plugin Check (PCP) compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.