dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-14166

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 WPMasterToolKit plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.13.0. This is due to the plugin allowing Author-level users to create and execute arbitrary PHP code through the Code Snippets feature without proper capability checks. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server, leading to remote code execution, privilege escalation, and complete site compromise.

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 WPMasterToolKit WordPress plugin (versions up to 2.13.0) contains a Code Snippets feature that lacks proper capability checks, allowing Author-level and above users to create and execute arbitrary PHP code. This authenticated PHP code injection vulnerability enables remote code execution, privilege escalation, and complete site compromise.

MitigationUpdate the plugin to a version beyond 2.13.0 when available; alternatively, disable or remove the plugin until a patch is released, and review user role assignments to limit access to trusted administrators.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm WPMasterToolKit plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WPMasterToolKit' in the installed plugins list, or query the database: SELECT * FROM wp_options WHERE option_name = 'active_plugins';
    Affected if WPMasterToolKit appears in the list of active plugins
  2. Identify installed plugin version
    In Plugins list page, click on the plugin name to view details, or inspect the plugin main file header in wp-content/plugins/wpmastertoolkit/ for the 'Version' comment
    Affected if Version is 2.13.0 or lower (any version up to and including 2.13.0)
  3. Verify Code Snippets feature is enabled
    Look for a 'Code Snippets' menu item in the WordPress admin sidebar, or check plugin settings for an option enabling the snippets functionality
    Affected if A Code Snippets menu item or settings option exists and is accessible
  4. Check for Author-level or higher user accounts
    In WordPress admin, go to Users > All Users and review the role column, or query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities';
    Affected if Any user account has the Author role or higher (Administrator, Editor, or Author)
  5. Inspect existing code snippets for malicious content
    Access the Code Snippets admin page and review each saved snippet for unfamiliar or suspicious PHP code, or query: SELECT * FROM wp_options WHERE option_name LIKE '%wpmastertoolkit%snippets%';
    Affected if Unexpected or unauthorized PHP code snippets are present in the database

User is affected if WPMasterToolKit plugin version 2.13.0 or lower is installed, the Code Snippets feature is enabled, and any user with Author-level access exists on the site.

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 a version beyond 2.13.0 when available; alternatively, disable or remove the plugin until a patch is released, and review user role assignments to limit access to trusted administrators.

Recommended fix Moderate confidence

2.13.1 or later (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WPMasterToolKit in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the Code Snippets feature now includes proper capability checks
  6. 6. Review user roles (Contributor and above) to ensure only trusted users have access
Caveat Review custom code snippets after upgrade to ensure compatibility with updated plugin version

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 / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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 locally
dbcve dependency scanner

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