phpinfo() WP · Security record
Is phpinfo() WP safe?
No known vulnerability affects the current version (8.0.7). 2 issues were found in earlier versions and fixed, the latest disclosed on Jun 19, 2024.
Checked 3 days ago against the WPVulnerability database, for version 8.0.7.
How it’s looked after
- Last release
- Oct 28, 2026 (1 week ago)
- Releases in the last year
- 8
- Tested up to
- WordPress 7.1.4
- Active installs
- 3K+
2 known vulnerabilities
- 1 high
- 1 medium
None affects the current version.
Disclosed each year
- 20231
- 20241
Every known vulnerability in phpinfo() WP
Newest first, with any that affect the current version at the top.
Fixed in 6.0 · CVE-2024-35776 · Jun 19, 2024 · Wordfence
Fixed in 5.0 · CVE-2023-26542 · Feb 24, 2023 · Wordfence
Questions about phpinfo() WP’s security
Is phpinfo() WP safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep phpinfo() WP updated: most attacks target sites that haven’t updated.
Does phpinfo() WP have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep phpinfo() WP up to date.
Is phpinfo() WP still maintained?
Yes. Its last release was 1 week ago. No support threads were opened in the last two months.
Is phpinfo() WP 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.