CVE-2025-32555
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 Edamam SEO, Nutrition and Print for Recipes by Edamam seo-nutrition-and-print-for-recipes-by-edamam allows Stored XSS.This issue affects SEO, Nutrition and Print for Recipes by Edamam: from n/a through <= 3.3.
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 confidenceA CSRF vulnerability in the Edamam SEO, Nutrition and Print for Recipes WordPress plugin (versions up to 3.3) allows attackers to inject malicious JavaScript via stored XSS. The lack of proper nonce verification on form submissions enables authenticated administrators to be tricked into unknowingly submitting crafted requests that persist malicious payloads in the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify if the Edamam plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Edamam SEO, Nutrition and Print for Recipes' or check the wp-content/plugins directory for a folder containing 'edamam' in the nameAffected if The plugin appears in the installed plugins list
-
Check the installed version numberIn WordPress admin, find the Edamam plugin in the Plugins list and note the version displayed beneath the plugin name; alternatively, open the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if The version is 3.3 or lower, or if no version is displayed and the plugin has not been updated recently
-
Inspect plugin admin forms for nonce fieldsView the page source of any admin settings page provided by the Edamam plugin; search for an HTML input field with name containing 'nonce' or '_wpnonce' within the form tagsAffected if No nonce or _wpnonce input field is found in the plugin's admin forms, indicating lack of CSRF protection
-
Examine stored data for suspicious script tagsUse a database query or WordPress admin to inspect any custom fields, options, or post meta that the Edamam plugin creates; look for <script> tags, javascript: URIs, or onload/onerror attributes in the stored valuesAffected if Any stored values contain executable JavaScript or HTML script tags that were not intentionally added by an administrator
A user is affected if the Edamam SEO, Nutrition and Print for Recipes plugin is installed at version 3.3 or lower and its admin forms lack nonce verification, allowing stored XSS payloads to persist in the database.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all form submissions and admin actions, and apply proper output escaping when rendering user-supplied data to prevent stored XSS execution.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32555 — 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-2025-32555 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