Spice Blocks
spice-blocks · plugin
Known security vulnerabilities for Spice Blocks. Find out in seconds which version runs on your site with WP Lens.
2 known vulnerabilities
2 exploitable without logging in · 1 with no official fix seen · latest Jun 9, 2025
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 2 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 2.0.7.7 · last updated Feb 9, 2026 · 900+ installs
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- High 7.5
CVE-2025-48130unauthenticated≤ 2.0.7.4
WordPress Spice Blocks plugin <= 2.0.7.4 - Arbitrary File Download vulnerability
- High 7.5
CVE-2025-39532unauthenticatedno fix seen
WordPress Spice Blocks plugin <= 2.0.7.7 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (2.0.7.7) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.