Spice Blocks · Security record
Is Spice Blocks safe?
One known vulnerability affects the current version (2.0.7.7), and it has no fix yet.
Checked 3 days ago against the WPVulnerability database, for version 2.0.7.7.
How it’s looked after
- Last release
- Feb 9, 2026 (9 months ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Active installs
- 900+
3 known vulnerabilities
- 3 high
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20231
- 20252
Every known vulnerability in Spice Blocks
Newest first, with any that affect the current version at the top.
Affects the current version · No fix yet · CVE-2025-39532 · Apr 17, 2025 · Wordfence
Fixed in 2.0.7.5 · CVE-2025-48130 · Jun 4, 2025 · Wordfence
Fixed in 1.3 · CVE-2023-33999 · Jul 18, 2023 · WPScan
Questions about Spice Blocks’s security
Is Spice Blocks safe to use?
Yes: 1 known vulnerability affects version 2.0.7.7, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Spice Blocks have known security vulnerabilities?
Yes: 1 known vulnerability affects version 2.0.7.7, according to WPVulnerability’s database.
Is Spice Blocks still maintained?
Its last release was 9 months ago. No support threads were opened in the last two months.
Is Spice Blocks compatible with the latest WordPress?
Spice Blocks’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
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.