CVE-2026-125948 · Package
NO FIX YET
The Recipe Card Blocks Lite WordPress plugin (up to and including 3.7.0) does not sanitize the steps text field of its recipe block. A logged-in Contributor can save a script in that field, and it runs in the browser of any visitor, including editors and administrators who preview or publish the post.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Recipe Card Blocks Lite plugin at version 3.7.0 or earlier, where users with Contributor access or higher can write posts. Sites without the plugin, or where only trusted editors write content, are less exposed. The sources do not state a fixed version.
Not affected if plugin-not-installed, trusted-authors-only
Who cares recipe-card-blocks-lite, self-hosted, wordpress
wp plugin get recipe-card-blocks-lite --field=version3.7.0 or earlierNo fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.