dbcve.org
CookedWordPress extension · Boxystudio

CVE-2023-44477

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-02
Fix available
A fix is available. Upgrade to after 1.7.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Boxy Studio Cooked plugin <= 1.7.13 versions.

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 confidence

Authenticated users with contributor+ privileges can inject malicious JavaScript via the Cooked plugin's recipe content fields. The XSS is stored in the database and executes when other users (including admins) view the affected recipe pages, allowing session hijacking or defacement.

MitigationUpdate Cooked plugin to version >1.7.13. If unable to update immediately, disable the plugin or restrict contributor-level posting permissions pending the patch.

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
Affected:<= 1.7.13

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cooked plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cooked' by Boxystudio, or check the plugin files in /wp-content/plugins/ for the cooked folder and review the main plugin file header for version number
    Affected if Cooked plugin version <= 1.7.13 is installed and active
  2. Confirm contributor-level access exists
    Go to WordPress Users > Roles and verify that users with 'Contributor' role have the capability to create or edit recipes (usually 'publish_recipes' or similar recipe-related capabilities)
    Affected if Contributor users can create or edit recipe content without admin approval
  3. Scan recipe content fields for XSS payloads
    Query the WordPress database: SELECT ID, post_title, post_content FROM wp_posts WHERE post_type = 'recipe' AND (post_content LIKE '%<script%' OR post_content LIKE '%onerror=%' OR post_content LIKE '%onload=%' OR post_content LIKE '%javascript:%'); Alternatively, manually review recent recipe posts in the WordPress admin under Recipes > All Recipes
    Affected if Any recipe records contain unsanitized HTML/JavaScript in recipe content fields (ingredients, instructions, description) that could execute in a browser

You are affected if Cooked plugin version 1.7.13 or lower is installed, contributor users can post recipes, and malicious script tags exist in any recipe content fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.7.13
Interim mitigation

Update Cooked plugin to version >1.7.13. If unable to update immediately, disable the plugin or restrict contributor-level posting permissions pending the patch.

Recommended fix Moderate confidence

Latest available version of Cooked plugin (version > 1.7.13)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Cooked' plugin by Boxy Studio
  4. 4. Check if an update is available and update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful and test that the plugin functions normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cooked Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-44477 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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