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