Live › vulnerability › CVE-2026-77829
Go to dashboardThe Cooked recipe management plugin for WordPress does not sanitize content passed to its [cooked-timer] shortcode, in all versions up to and including 1.16.1. A contributor-level user can store a script in a page that runs in the browser of anyone who opens it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Cooked plugin at version 1.16.1 or earlier that let contributor-level or higher users create pages or posts using the [cooked-timer] shortcode. Sites without the plugin, or where only trusted editors write content, have lower exposure. Note that stored script runs for every visitor who opens the injected page, including administrators.
No product ranges from the sources yet.
1.16.1 are affected.[cooked-timer] shortcode to find where it is used.1.16.1; the sources do not name the fixed version, so check the plugin's changelog.[cooked-timer] shortcode from content written by untrusted contributors.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Cooked – Recipe Management plugin for WordPress is vulnerable to Stored Cross-Site Scripting via [cooked-timer] Shortcode Content in all versions up to, and including, 1.16.1 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-77829")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.