dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-15445

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Restaurant Cafeteria WordPress theme through 0.4.6 exposes insecure admin-ajax actions without nonce or capability checks, allowing any logged-in user, like subscriber, to perform privileged operations. An attacker can install and activate a from a user-supplied URL, leading to arbitrary PHP code execution, and also import demo content that rewrites site configuration, including Restaurant Cafeteria WordPress theme through 0.4.6_mods, pages, menus, and front page settings.

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 Restaurant Cafeteria WordPress theme through version 0.4.6 exposes AJAX handlers via admin-ajax.php without nonce verification or capability checks. Any authenticated user (including low-privilege subscribers) can trigger these endpoints to install/activate plugins from arbitrary URLs leading to arbitrary PHP code execution, and to import demo content that overwrites theme settings, pages, menus, and front page configuration.

MitigationAdd nonce verification and current_user_can() capability checks to all admin-ajax action handlers in the theme, or update to a patched version if available from the vendor.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 if Restaurant Cafeteria theme is installed
    Check wp-content/themes/ directory for a folder named 'restaurant-cafeteria' or similar theme directory. List all installed themes via WordPress admin under Appearance > Themes or inspect the filesystem.
    Affected if The theme folder exists in the WordPress themes directory.
  2. Determine the installed theme version
    Open the theme's style.css file (typically at wp-content/themes/restaurant-cafeteria/style.css) and locate the 'Version:' header in the theme comments at the top of the file.
    Affected if The version number is 0.4.6 or lower (including any 0.x.x version through 0.4.6).
  3. Verify WordPress admin-ajax.php is accessible
    Confirm that the WordPress site has admin-ajax.php at /wp-admin/admin-ajax.php or /wp-admin/admin-ajax.php (accessible via the web). This is the entry point for the vulnerable AJAX handlers.
    Affected if admin-ajax.php is present and responds to requests.
  4. Check for registered AJAX action handlers in the theme
    Inspect the theme's functions.php file (and any included files) for calls to add_action('wp_ajax_', ...) or add_action('wp_ajax_nopriv_', ...) that register AJAX handlers. Look for actions related to plugin installation, plugin activation, or demo content import.
    Affected if The theme registers AJAX handlers for plugin installation, plugin activation, or demo import without capability checks.
  5. Test if low-privilege users can trigger the endpoints
    Log in as a subscriber-level user and make a POST request to /wp-admin/admin-ajax.php with an action parameter matching one of the theme's AJAX handlers (e.g., action=theme_install_plugin, action=theme_activate_plugin, or action=theme_import_demo). Check if the request is processed without a 403 error or nonce validation failure.
    Affected if The AJAX endpoint accepts requests from authenticated users with subscriber-level privileges without returning an error.

If the Restaurant Cafeteria theme version 0.4.6 or lower is installed and the site has authenticated users (any role including subscriber), the environment is affected by this vulnerability.

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

Add nonce verification and current_user_can() capability checks to all admin-ajax action handlers in the theme, or update to a patched version if available from the vendor.

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-2025-15445 — 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-2025-15445 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