CVE-2024-13011
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 · uneditedThe WP Foodbakery plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the 'upload_publisher_profile_image' function in versions up to, and including, 4.7. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 confidenceThe WP Foodbakery plugin for WordPress contains an arbitrary file upload vulnerability in the 'upload_publisher_profile_image' function. The function fails to properly validate file types, allowing unauthenticated attackers to upload arbitrary files including executable PHP scripts. This can lead to remote code execution on the affected server.
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
- 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.
-
Confirm WP Foodbakery plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Foodbakery' or check the plugins directory (wp-content/plugins/) for the foodbakery folderAffected if The plugin is present on the WordPress installation
-
Identify installed WP Foodbakery versionCheck the plugin header in foodbakery.php or view the plugin details in WordPress admin Plugins page - the version number is displayed thereAffected if The installed version is lower than 4.8 (versions prior to 4.8 are vulnerable)
-
Verify vulnerable endpoint existsCheck if the file wp-content/plugins/foodbakery/include/upload_publisher_profile_image.php or similar path exists and is accessible via HTTPAffected if The upload_publisher_profile_image endpoint is present and responds to requests
-
Inspect upload directory for unexpected filesCheck the plugin's upload directory (typically wp-content/uploads/foodbakery/) for any .php files or other unexpected file types that should not be thereAffected if Arbitrary PHP files or executable scripts are found in upload directories
If WP Foodbakery plugin is installed with a version before 4.8 and the upload endpoint is accessible, the environment is affected by this arbitrary file upload 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.
From vendor dataUpdate the WP Foodbakery plugin to version 4.8 or later which includes proper file type validation. If no patch is available, disable the plugin immediately or deploy a WAF rule to block unauthorized file uploads to the upload_publisher_profile_image endpoint.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13011 — 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-13011 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