Website support, maintenance and fixes for UK businessesCall 0208 088 8371info@websupportservices.co.uk

HomeWordPress vulnerabilitiesRecipe Card Blocks Lite

Recipe Card Blocks Lite vulnerabilities

Recipe Card Blocks Lite has 7 known vulnerabilities in this database. The most recent published record is dated 20 Nov 2026.

Known vulnerabilities
7
Active installs
10,000+
Latest version
3.6.4
Last updated
22 Oct 2026
Most recent
20 Nov 2026

No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.

Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.

VulnerabilitySeverityAffectedFixPublished
Broken access control
CVE-2026-130043
Medium 4.3Up to 4.0.1No fixed version yet2 d ago
Broken access control
CVE-2026-131587
Medium 4.3Up to 4.0.2No fixed version yet2 d ago
Cross-site scripting (XSS)
CVE-2026-125948
Medium 6.4Up to 3.7.0No fixed version yet9 d ago
Sensitive data exposure
CVE-2026-115282
Medium 5.3Before 3.6.4Fixed in 3.6.429 Oct 2026
SQL injection
CVE-2026-115281
Medium 6.8Before 3.6.4Fixed in 3.6.428 Oct 2026
Cross-site scripting (XSS)
CVE-2026-3011
Medium 6.4Up to 3.4.13Fixed in a later version (latest 3.6.4)8 Jun 2026
SQL injection
CVE-2025-14973
Medium 6.8Before 3.4.13Fixed in 3.4.1326 Jan 2026
Read the published descriptions
CVE-2026-130043, 20 Nov 2026
The Recipe Card Blocks Lite plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to overwrite the stored post_content of any post or page on the site, including published posts and private drafts authored by administrators or other users. CVE record
CVE-2026-131587, 20 Nov 2026
The Recipe Card Blocks Lite plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.2 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to overwrite the post_content of arbitrary posts on the site, including Administrator-owned published posts, bypassing the edit_others_posts and edit_published_posts capability checks. This vulnerability is only exploitable when the wpzoom_rcb_settings_synchronize_recipe_post setting is enabled, and requires the target post to contain at least one Recipe Card block whose twin can be matched to the attacker's draft recipe post. CVE record
CVE-2026-125948, 13 Nov 2026
The Recipe Card Blocks Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'steps[].text' parameter in all versions up to, and including, 3.7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because wp_kses_post() preserves block-delimiter HTML comments verbatim on save, a Contributor can embed event-handler payloads inside the block's steps[].text attribute in a draft or pending post without the unfiltered_html capability, and the payload executes for any visitor - including privileged editors and administrators who preview or publish the post - as well as through the public print endpoint. CVE record
CVE-2026-115282, 29 Oct 2026
The Recipe Card Blocks Lite WordPress plugin before 3.6.4 does not perform an authorization check before rendering posts through its recipe print feature, allowing unauthenticated users to disclose the title, ID and recipe content of unpublished posts, including drafts, pending, private and password-protected posts, that contain a recipe card block. Its optional "print only published posts" protection does not prevent this, because the status check is applied to a different post than the one ultimately rendered. CVE record
CVE-2026-115281, 28 Oct 2026
The Recipe Card Blocks Lite WordPress plugin before 3.6.4 does not sanitize and cast a block and shortcode attribute before concatenating it into SQL queries, allowing authenticated users with Contributor-level access or above to perform SQL injection attacks. CVE record
CVE-2026-3011, 8 Jun 2026
The Recipe Card Blocks Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the recipe block's 'summary' and 'notes' attributes in all versions up to, and including, 3.4.13. This is due to the 'WPZOOM_Helpers::deserialize_block_attributes' method converting unicode-encoded sequences back into HTML characters after sanitization has already been applied. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that execute whenever a user accesses the published post or the print view of an injected recipe. CVE record
CVE-2025-14973, 26 Jan 2026
The Recipe Card Blocks Lite WordPress plugin before 3.4.13 does not sanitize and escape a parameter before using it in a SQL statement, allowing contributors and above to perform SQL injection attacks. CVE record

What to do if you run Recipe Card Blocks Lite

If you run Recipe Card Blocks Lite, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.

If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.

Email me about new Recipe Card Blocks Lite vulnerabilities

Free. We email you when a new vulnerability is published for Recipe Card Blocks Lite, usually within minutes. Confirm by email; unsubscribe any time.

Focus on your business. We’ll take care of your website.

From everyday updates to ongoing care, we keep your website working.

Get website support