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