CVE-2026-73999

Cooked – Recipe Management <= 1.16.0 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-09-16 18:17
Nixxies

Strategic Overview

Status
Patched in 1.16.1
Affected Plugin
Cooked – Recipe Management
Affected Version
<= 1.16.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-73999
View all Cooked – Recipe Management vulnerabilities

At a glance

CVE-2026-73999 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Cooked WordPress plugin, affecting versions <= 1.16.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.16.1; sites on affected versions should update now. Disclosed September 2026, reported by Nixxies.

Vulnerability Overview

The Cooked – Recipe Management plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.16.0. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Cooked <= 1.16.0 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Cooked the fix is 1.16.1: builds <= 1.16.0 are affected, anything from 1.16.1 onward is not.

Remediation

Update to version 1.16.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Cooked 1.16.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-73999https://www.wordfence.com/threat-intel/vulnerabilities/id/ad4884f6-27b1-4fed-b724-e14c0312d089https://nvd.nist.gov/vuln/detail/CVE-2026-73999

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C