Vigilant · Security record
Is Vigilant safe?
No known vulnerability affects the current version (3.0.12). 1 issue was found in earlier versions and fixed, the latest disclosed on Sep 11, 2026.
Checked 4 days ago against the WPVulnerability database, for version 3.0.12.
How it’s looked after
- Last release
- Nov 8, 2026 (12 hours ago)
- Releases in the last year
- 98
- Tested up to
- WordPress 7.1.4
- Support resolved
- 26 of 27 threads in two months
- Active installs
- 4K+
1 known vulnerability
- 1 high
None affects the current version.
Every known vulnerability in Vigilant
Newest first, with any that affect the current version at the top.
Fixed in 2.10.3 · CVE-2026-81754 · Sep 11, 2026 · Wordfence
Questions about Vigilant’s security
Is Vigilant safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Vigilant updated: most attacks target sites that haven’t updated.
Does Vigilant have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Vigilant up to date.
Is Vigilant still maintained?
Yes. Its last release was 12 hours ago. Its authors resolved 26 of the 27 support threads opened in the last two months.
Is Vigilant 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.