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