CookedWordPress extension · Boxystudio
CVE-2024-49290
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in Gora Tech LLC Cooked Pro allows Cross Site Request Forgery.This issue affects Cooked Pro: from n/a before 1.8.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-Site Request Forgery (CSRF) vulnerability in Cooked Pro plugin allows attackers to trick authenticated users into performing unintended state-changing actions (such as modifying plugin settings or content) by exploiting the lack of anti-CSRF token validation on sensitive operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CookedWordPress extension
< 1.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Cooked plugin is installedNavigate to WordPress admin Dashboard > Plugins > Installed Plugins and look for 'Cooked' or 'Cooked Pro' by Boxystudio in the plugin listAffected if Cooked plugin is not found in the installed plugins list, then this CVE does not apply
-
Identify the installed Cooked versionIn the installed plugins list, locate the Cooked plugin entry and read the version number displayed beneath the plugin nameAffected if The version shown is below 1.8.0 (for example 1.7.9, 1.7.8, etc.)
-
Confirm plugin is the vulnerable componentVerify the plugin author is Boxystudio and the plugin name is 'Cooked' or 'Cooked Pro' - other cooking or recipe plugins from different authors are not affectedAffected if The plugin is from Boxystudio and named Cooked with version less than 1.8.0
-
Check for authenticated user accessReview the WordPress user roles active on the site - CSRF requires authenticated users (any role from Subscriber to Administrator) to be targetedAffected if The site has at least one authenticated user account and the vulnerable Cooked version is installed
If Cooked or Cooked Pro by Boxystudio is installed with a version number lower than 1.8.0, the environment is affected by this CSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.8.0
Upgrade Cooked Pro to version 1.8.0 or later which includes anti-CSRF token implementation. Additionally, ensure SameSite cookies are enabled and implement Origin/Referer header validation as defense-in-depth.
1.8.0
- 1. Back up your WordPress site database and files before performing any updates
- 2. Navigate to WordPress admin dashboard > Plugins
- 3. Locate the Cooked (or Cooked Pro) plugin in your installed plugins list
- 4. If an update is available, click 'Update Now' to upgrade to version 1.8.0
- 5. Alternatively, download version 1.8.0 from a trusted source and upload it via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin status shows version 1.8.0
- 7. Test critical functionality (recipe creation, frontend submission forms, admin actions) to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cooked
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49290 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data