dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13334

HIGH · 8.1 CVSS v3.1 Published 2025-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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 Blaze Demo Importer plugin for WordPress is vulnerable to unauthorized database resets and file deletion due to a missing capability check on the "blaze_demo_importer_install_demo" function in all versions up to, and including, 1.0.13. This makes it possible for authenticated attackers, with subscriber level access and above, to reset the database by truncating all tables (except options, usermeta, and users), delete all sidebar widgets, theme modifications, and content of the uploads folder.

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 Blaze Demo Importer WordPress plugin lacks a capability check on the blaze_demo_importer_install_demo function, allowing any authenticated user with subscriber-level access or higher to trigger destructive database operations including truncating tables, deleting widgets, clearing theme modifications, and wiping the uploads folder. This is a privilege escalation/IDOR vulnerability where low-privileged users can execute admin-level functions.

MitigationImmediately update to version 1.0.14 or later which adds proper capability verification. Until then, disable the plugin or restrict user registration to prevent exploitation by unauthorized subscribers.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Verify Blaze Demo Importer plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Blaze Demo Importer' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a blaze-demo-importer folder
    Affected if The plugin is installed and active - proceed to version check
  2. Check installed plugin version
    In WordPress Admin > Plugins, click on the Blaze Demo Importer plugin to view its details, or open the main plugin PHP file (usually blaze-demo-importer.php) and locate the 'Version' header in the plugin comments
    Affected if Version is unknown, empty, or below 1.14 - the vulnerability likely exists
  3. Inspect the vulnerable function for capability checks
    Open the main plugin file and locate the 'blaze_demo_importer_install_demo' function. Search for 'current_user_can' or 'manage_options' or similar WordPress capability checks within that function
    Affected if No capability check (such as 'manage_options' or 'edit_theme_options') is found before the destructive operations - the vulnerability is present
  4. Review user role assignments
    In WordPress Admin > Users, list all users and their assigned roles. Note any users with 'Subscriber', 'Contributor', 'Author', or 'Editor' roles
    Affected if Any user with subscriber-level or higher access exists - the flaw could be exploited by these users
  5. Audit recent database and file modifications
    Check database tables (excluding options, usermeta, users) for recent truncation events, review /wp-content/uploads/ folder for unexpected emptiness, and check sidebar widget configurations in the database for recent deletions
    Affected if Unexpected mass deletions, empty uploads folder, or missing widgets are found - possible exploitation has occurred

If the Blaze Demo Importer plugin is installed with a version before 1.14 and lacks capability checks in the blaze_demo_importer_install_demo function, the environment is affected by this authorization bypass 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update to version 1.0.14 or later which adds proper capability verification. Until then, disable the plugin or restrict user registration to prevent exploitation by unauthorized subscribers.

Recommended fix High confidence

Version 1.0.14 or later of the Blaze Demo Importer plugin

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Blaze Demo Importer plugin
  4. Check if an update to version 1.0.14 or later is available
  5. If an update is available, click 'Update Now' to install the patched version
  6. If no automatic update is available, manually download version 1.0.14 or later from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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