NextGEN Custom Fields · Security record
Is NextGEN Custom Fields safe?
No known vulnerabilities are on record for NextGEN Custom Fields.
Checked 2 days ago against the WPVulnerability database, for version 1.2.5.
How it’s looked after
- Last release
- Jan 19, 2024 (2 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.4.14 (current: 7.1)
- Active installs
- 1K+
Known vulnerabilities
None on record for NextGEN Custom Fields.
Questions about NextGEN Custom Fields’s security
Is NextGEN Custom Fields safe to use?
No known vulnerabilities are on record for NextGEN Custom Fields. That isn’t a guarantee, so keep it updated like any plugin.
Does NextGEN Custom Fields have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for NextGEN Custom Fields.
Is NextGEN Custom Fields still maintained?
Its last release was 2 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is NextGEN Custom Fields compatible with the latest WordPress?
NextGEN Custom Fields’s readme says it’s tested up to WordPress 6.4.14, 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.