dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12920

HIGH · 8.8 CVSS v3.1 Published 2025-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The FoodBakery | Delivery Restaurant Directory WordPress Theme theme for WordPress is vulnerable to unauthorized access of data and modification of data due to a missing capability check on the foodbakery_var_backup_file_delete, foodbakery_widget_file_delete, theme_option_save, export_widget_settings, ajax_import_widget_data, foodbakery_var_settings_backup_generate, foodbakery_var_backup_file_restore, and theme_option_rest_all functions in all versions up to, and including, 4.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files, update theme options, export widget options, import widget options, generate backups, restore backups, and reset theme options.

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 confidence

The FoodBakery WordPress theme has multiple AJAX action functions (foodbakery_var_backup_file_delete, foodbakery_widget_file_delete, theme_option_save, export_widget_settings, ajax_import_widget_data, foodbakery_var_settings_backup_generate, foodbakery_var_backup_file_restore, and theme_option_rest_all) that lack proper capability/authorization checks. These functions are accessible to any authenticated user with Subscriber-level access, allowing privilege escalation to delete arbitrary files, modify theme options, and manage backups/settings.

MitigationUpdate to theme version 4.8 or later which should include proper capability checks; alternatively, disable user registration or implement a firewall/WAF to block unauthenticated access to these AJAX endpoints until patched.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify FoodBakery theme installation and version
    Check the theme's style.css file in wp-content/themes/foodbakery/ for the 'Version:' header, or query the WordPress themes API endpoint /wp-admin/admin-ajax.php?action=theme_version_check if available
    Affected if The installed version is lower than 4.8 or cannot be determined
  2. Verify if user registration is enabled
    Navigate to WordPress Settings > General > 'Membership' and check 'Anyone can register', or query the site via wp-cli: wp option get users_can_register
    Affected if User registration is enabled and new subscriber-level accounts can be created
  3. Inspect user roles for unauthorized accounts
    List all user accounts via WordPress admin Users panel or wp-cli: wp user list --role=subscriber --fields=ID,user_login,user_email
    Affected if There are subscriber accounts that were created without manual admin approval or contain unexpected usernames
  4. Check theme options for unauthorized modifications
    Review theme options in Appearance > Theme Options, or inspect the wp_options table for modified foodbakery_var_ settings entries
    Affected if Theme options have been changed unexpectedly, or unfamiliar values exist in foodbakery-related option names
  5. Audit AJAX action accessibility
    Test access to the vulnerable AJAX actions using a low-privilege (subscriber) account by sending POST requests to /wp-admin/admin-ajax.php with actions such as foodbakery_var_backup_file_delete or theme_option_save
    Affected if The AJAX endpoints accept and process requests from authenticated subscriber-level users without returning a capability error

A user is affected if the FoodBakery theme version is below 4.8 AND user registration is enabled, allowing any subscriber-level account to access privileged AJAX functions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to theme version 4.8 or later which should include proper capability checks; alternatively, disable user registration or implement a firewall/WAF to block unauthenticated access to these AJAX endpoints until patched.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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