Recipe Card Blocks Lite
recipe-card-blocks-by-wpzoom · plugin
Known security vulnerabilities for Recipe Card Blocks Lite. Find out in seconds which version runs on your site with WP Lens.
8 known vulnerabilities
3 exploitable without logging in · latest Aug 18, 2026
Before you install
Use with care
- 2 records needing no login published in the last two years.
If you install it, keep auto-updates on and monitor the site: when a new record appears you need to update quickly.
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 3.6.3 · last updated Oct 16, 2026 · 10K+ installs
wordpress.org status checked on Oct 18, 2026
Vulnerabilities
- High 8.8
CVE-2024-43293login required≤ 3.3.1
WordPress Recipe Card Blocks for Gutenberg & Elementor plugin <= 3.3.1 - Broken Access Control vulnerability
- High 7.1
CVE-2026-73361unauthenticated · needs a click≤ 3.4.18
WordPress Recipe Card Blocks for Gutenberg & Elementor plugin <= 3.4.18 - Cross Site Scripting (XSS) vulnerability
- Medium 6.8
CVE-2025-14973contributor+→ 3.4.13
Recipe Card Blocks < 3.4.13 - Contributor+ SQLi
- Medium 6.5
CVE-2025-62019unauthenticated≤ 3.4.8
WordPress Recipe Card Blocks for Gutenberg & Elementor plugin <= 3.4.8 - Broken Access Control vulnerability
- Medium 6.4
CVE-2026-3011author+≤ 3.4.13
Recipe Card Blocks Lite <= 3.4.13 - Authenticated (Author+) Stored Cross-Site Scripting via 'summary' and 'notes'
- Medium 6.1
CVE-2021-24632unauthenticated · needs a click→ 2.8.1
Recipe Card Blocks < 2.8.1 - Reflected Cross-Site Scripting
- Medium 5.4
CVE-2021-24634contributor+→ 2.8.3
Recipe Card Blocks < 2.8.3 - Contributor+ Stored Cross-Site Scripting
- Medium 4.3
CVE-2025-26983login required≤ 3.4.3
WordPress Recipe Card Blocks for Gutenberg & Elementor plugin <= 3.4.3 - 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).