dbcve.org
Ziplist RecipeWordPress extension · Condenast

CVE-2025-28868

HIGH · 8.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to after 3.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in ZipList ZipList Recipe ziplist-recipe-plugin allows Cross Site Request Forgery.This issue affects ZipList Recipe: from n/a through <= 3.1.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the ZipList Recipe plugin (version <= 3.1) allows attackers to trick authenticated users into performing unintended state-changing actions. The plugin lacks proper anti-CSRF token validation on form submissions or AJAX requests, enabling attackers to craft malicious requests that execute with the victim's privileges.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing operations including form submissions and AJAX calls, and verify the nonce validity server-side before processing requests.

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
Ziplist RecipeWordPress extension
Affected:<= 3.1

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
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 checks

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

  1. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Ziplist Recipe' or 'Condenast Ziplist Recipe' in the plugin list. Note the version number displayed.
    Affected if The plugin is installed and the version is 3.1 or lower.
  2. Identify state-changing endpoints
    Review the plugin directory (wp-content/plugins/ziplist-recipe) for PHP files containing form handlers, AJAX actions (wp_ajax_* hooks), or admin action hooks (admin_post_*) that modify recipe data or plugin settings.
    Affected if The plugin contains any admin action handlers or AJAX endpoints that process state-changing requests without explicit mention of nonce verification.
  3. Verify nonce implementation in plugin code
    Open the main plugin PHP file and search for occurrences of 'wp_nonce_field', 'wp_create_nonce', 'check_admin_referer', or 'wp_verify_nonce' across all plugin files. Compare the number of nonce implementations against the number of form submissions and AJAX handlers found.
    Affected if Sensitive endpoints (forms modifying recipes, plugin settings, or data submissions) lack corresponding nonce verification calls.
  4. Test referer origin validation
    If you have a staging environment, attempt a cross-origin form submission to a plugin endpoint (such as saving a recipe or updating settings) while observing whether the request is rejected based on the HTTP Referer or Origin header.
    Affected if The plugin accepts and processes state-changing requests without validating the request origin or referer header.

A user is affected if the Condenast Ziplist Recipe plugin version 3.1 or lower is installed and the plugin processes state-changing requests (recipe edits, settings changes) without verifying anti-CSRF tokens or request origin.

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.

From vendor data
Upgrade available Upgrade to a release after 3.1
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all state-changing operations including form submissions and AJAX calls, and verify the nonce validity server-side before processing requests.

Fix this in Ziplist Recipe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-28868 — 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-2025-28868 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