Is WPVulnerability safe?

No known vulnerability affects the current version (5.1.6). 1 issue was found in earlier versions and fixed, the latest disclosed on Mar 18, 2026.

Checked 1 day ago against the WPVulnerability database, for version 5.1.6.

How it’s looked after

Last release: Aug 23, 2026 (2 months ago)
Releases in the last year: 10
Tested up to: WordPress 7.1.4
Support resolved: 2 of 4 threads in two months
Active installs: 10K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in WPVulnerability

Newest first, with any that affect the current version at the top.

medium
Missing Authorization
Fixed in 4.2.1.1 · CVE-2026-24376 · Mar 18, 2026 · Wordfence

Questions about WPVulnerability’s security

Is WPVulnerability safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WPVulnerability updated: most attacks target sites that haven’t updated.

Does WPVulnerability have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep WPVulnerability up to date.

Is WPVulnerability still maintained?

Yes. Its last release was 2 months ago. Its authors resolved 2 of the 4 support threads opened in the last two months.

Is WPVulnerability 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 free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.