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