Post/Page Specific Custom Code · Security record
Is Post/Page Specific Custom Code safe?
No known vulnerabilities are on record for Post/Page Specific Custom Code.
Checked 3 days ago against the WPVulnerability database, for version 0.3.1.
How it’s looked after
- Last release
- Jul 23, 2026 (3 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 7.0.8
- Active installs
- 6K+
Known vulnerabilities
None on record for Post/Page Specific Custom Code.
Questions about Post/Page Specific Custom Code’s security
Is Post/Page Specific Custom Code safe to use?
No known vulnerabilities are on record for Post/Page Specific Custom Code. That isn’t a guarantee, so keep it updated like any plugin.
Does Post/Page Specific Custom Code have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for Post/Page Specific Custom Code.
Is Post/Page Specific Custom Code still maintained?
Yes. Its last release was 3 months ago. No support threads were opened in the last two months.
Is Post/Page Specific Custom Code 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.