PatchSiren cyber security CVE debrief
CVE-2026-77829 goratech CVE debrief
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. This vulnerability allows 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. Defenders should assess exposure and prioritize verification and updates to prevent potential XSS attacks. The vulnerability exists due to insufficient input sanitization and output escaping.
- Vendor
- goratech
- Product
- Cooked – Recipe Management
- CVSS
- MEDIUM 6.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-16
- Original CVE updated
- 2026-10-16
- Advisory published
- 2026-10-16
- Advisory updated
- 2026-10-16
Who should care
Defenders responsible for WordPress installations with the Cooked – Recipe Management plugin should assess exposure and prioritize verification and updates to prevent potential XSS attacks.
Why it matters
The Cooked – Recipe Management plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing authenticated attackers to inject arbitrary web scripts. Defenders should prioritize verification and updates to prevent potential XSS attacks.
- Potential for authenticated attackers to inject arbitrary web scripts
- Possible execution of injected scripts when users access affected pages
- Need for verification and updates to prevent potential XSS attacks
- Importance of monitoring for potential XSS attacks
Technical summary
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.
Defensive priority
Defenders should prioritize verifying and updating the Cooked – Recipe Management plugin to prevent potential XSS attacks.
Recommended defensive actions
- Verify and update the Cooked – Recipe Management plugin to the latest version.
- Monitor for potential XSS attacks.
- Implement additional security measures to prevent similar vulnerabilities.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, confirming it affects versions up to 1.16.1 of the Cooked – Recipe Management plugin. Further verification is needed to confirm affected versions and potential impact. Defenders should verify the plugin version and assess exposure. Evidence from the CVE Program and NVD detail page supports this assessment.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-77829 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-77829
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-77829 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-77829
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://plugins.trac.wordpress.org/browser/cooked/tags/1.16.0/includes/class.cooked-shortcodes.php
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.