CVE-2025-0180
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 privilege escalation in all versions up to, and including, 4.7. This is due to the plugin not properly restricting what user meta can be updated during profile registration. This makes it possible for unauthenticated attackers to register on the site as an administrator.
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 WordPress plugin versions up to 4.7 fails to properly restrict which user metadata fields can be modified during the profile registration process. This allows unauthenticated attackers to register new accounts with administrative privileges by supplying elevated user role metadata during registration, effectively granting them full admin access to the WordPress site.
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 installedNavigate to WordPress admin > Plugins and look for 'WP Foodbakery' in the installed plugins list, or check the plugin files in wp-content/plugins/foodbakery/ for a version fileAffected if The plugin is present on the WordPress site
-
Identify the installed plugin versionIn WordPress admin > Plugins, click on the WP Foodbakery plugin to view its version number, or open the main plugin PHP file and look for a Version: comment or constantAffected if The version is 4.7 or any version below 4.8 (the plugin shows version 4.7 or lower)
-
Verify if WordPress user registration is enabledGo to WordPress admin > Settings > General and check the 'Membership' setting 'Anyone can register' is checked, or query the site_options table for option_name 'users_can_register' set to 1Affected if User registration is enabled on the site (anyone can register is checked)
-
Audit existing administrator accounts for unauthorized creationsNavigate to WordPress admin > Users and review all accounts with Administrator role, noting registration dates and email addresses. Cross-reference with expected admin usersAffected if There are administrator accounts created recently that were not created by known site administrators, or there are admin accounts with unexpected email domains
You are affected if the WP Foodbakery plugin version is 4.7 or lower AND user registration is enabled on the site, regardless of whether you see exploitation evidence.
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.
dbcve · scopedUpdate the WP Foodbakery plugin to version 4.8 or later. Until updated, disable user registration on the site and audit existing administrator accounts for any unauthorized access.
4.8
- Update the WP Foodbakery plugin to version 4.8 or later via the WordPress plugin repository or your site's plugin management interface
- Verify that new user registrations are properly restricted after the update
- Ensure only intended user roles can be created during registration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0180 — 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-0180 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