FoodbakeryWordPress extension · Chimpgroup
CVE-2025-32927
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 · uneditedDeserialization of Untrusted Data vulnerability in Chimpstudio FoodBakery wp-foodbakery allows Object Injection.This issue affects FoodBakery: 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 confidenceThis is a PHP Object Injection vulnerability in the FoodBakery WordPress plugin. The deserialization of untrusted data occurs when the application uses PHP's unserialize() function on data that can be controlled by an attacker, potentially allowing remote code execution through malicious serialized objects.
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
FoodbakeryWordPress extension
<= 3.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 FoodBakery plugin is installedNavigate to WordPress admin > Plugins and look for 'FoodBakery' by Chimpgroup, or check the /wp-content/plugins/ directory for the foodbakery folderAffected if The FoodBakery plugin folder exists in the WordPress installation
-
Determine installed FoodBakery versionCheck the plugin main file (usually foodbakery.php) for the 'Version' header, or view the plugin in WordPress admin which displays the version numberAffected if The installed version is 3.3 or lower
-
Identify if user input reaches deserializationSearch plugin PHP files for unserialize() calls, particularly those processing $_GET, $_POST, $_REQUEST, or cookie values. Check files that handle plugin settings, shortcodes, or AJAX endpointsAffected if The plugin code contains unserialize() applied to any user-supplied input without validation
-
Check for active gadget chainsReview all installed plugins and themes for potential PHP object injection gadget chains. Common indicators include __wakeup, __destruct, or __toString methods in other plugins that could be chained with the deserialization pointAffected if Additional plugins or themes contain magic methods (__wakeup, __destruct, __toString) that could be triggered by the injected objects
A WordPress site is affected if it has FoodBakery plugin version 3.3 or lower installed AND the plugin uses unserialize() on untrusted user input, which could allow injection of arbitrary PHP objects.
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 dataUpdate FoodBakery to the latest patched version immediately. If no patch is available, disable the plugin or implement input validation to ensure untrusted data never reaches unserialize() calls.
Fix this in Foodbakery
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32927 — 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-32927 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