dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14364

HIGH · 8.8 CVSS v3.1 Published 2025-12-18
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 Demo Importer Plus plugin for WordPress is vulnerable to unauthorized modification of data, loss of data, and privilege escalation due to a missing capability check on the Ajax::handle_request() function in all versions up to, and including, 2.0.8. This makes it possible for authenticated attackers, with Subscriber-level access and above, to trigger a full site reset, dropping all database tables except users/usermeta and re-running wp_install(), which also assigns the Administrator role to the attacking subscriber account.

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 Demo Importer Plus WordPress plugin lacks a capability check on the Ajax::handle_request() function, allowing any authenticated user with Subscriber-level access or higher to trigger a destructive full site reset that drops all database tables except users/usermeta and re-executes wp_install(), simultaneously elevating the attacker's account to Administrator role.

MitigationUpdate the plugin to version 2.0.9 or later which adds proper capability verification; if the site may have been compromised, restore from a clean backup and verify user account integrity.

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. Locate the Demo Importer Plus plugin files
    Check for the plugin directory at /wp-content/plugins/demo-importer-plus/ or search for files containing 'Demo_Importer_Plus' in the plugin directory
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin file (usually demo-importer-plus.php) and locate the Version header in the plugin comment block, or check the version in the plugin's readme.txt file
    Affected if The version is lower than 2.0.9 or the version cannot be determined (indicating an unpatched pre-2.0.9 release)
  3. Inspect the Ajax class for the handle_request method
    Locate the class-ajax.php or similar file in the plugin directory and search for the handle_request() function; examine whether it contains a capability check (such as current_user_can('manage_options') or 'manage_options' capability verification) before executing reset logic
    Affected if The handle_request() function exists and lacks a capability check before performing database operations
  4. Verify the reset/install functionality is accessible
    Check if the plugin registers Ajax actions (wp_ajax_* hooks) that map to the handle_request method without requiring administrator-level permissions; examine the add_action calls for wp_ajax_demo_importer_plus_* handlers
    Affected if Ajax endpoints are registered without proper capability checks (e.g., no current_user_can('manage_options') before processing)
  5. Check for subscriber-level access presence
    Review user role configurations and confirm whether Subscriber role exists on the site, as the vulnerability allows any authenticated user with Subscriber-level access to trigger the attack
    Affected if Subscriber role or any authenticated user role is enabled on the WordPress site

A user is affected if the Demo Importer Plus plugin is installed with a version prior to 2.0.9 and the handle_request() function lacks proper capability verification, allowing any authenticated user to reset the site and gain admin access.

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

Update the plugin to version 2.0.9 or later which adds proper capability verification; if the site may have been compromised, restore from a clean backup and verify user account integrity.

Recommended fix Moderate confidence

Upgrade to the latest version of Demo Importer Plus (version 2.0.9 or higher)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Demo Importer Plus' in the plugin list
  4. Check if the current version is 2.0.8 or below
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the updated plugin from wordpress.org/plugins/demo-importer-plus and upload it
  6. After updating, verify the new version number in the Plugins list
  7. Test that the site functionality remains intact

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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