CVE-2026-25447
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Jonathan Daggerhart Widget Wrangler widget-wrangler allows Code Injection.This issue affects Widget Wrangler: from n/a through <= 2.3.9.
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 · low confidenceA code injection vulnerability exists in the Widget Wrangler WordPress plugin (versions up to 2.3.9) by Jonathan Daggerhart. The vulnerability allows attackers to inject malicious code into the application due to improper control of code generation. With a CVSS score of 9.1, this critical flaw can lead to complete compromise of the WordPress site, including data theft, malware injection, or full administrative access.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Widget Wrangler plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the widget-wrangler folderAffected if The widget-wrangler plugin directory exists in the WordPress plugins folder
-
Identify installed Widget Wrangler versionIn WordPress admin, find Widget Wrangler in the plugins list and read the version number displayed beneath the plugin name, or open and read the main plugin file (widget-wrangler.php) to find the Version header commentAffected if The installed version is 2.3.9 or lower (any version through 2.3.9 is affected)
-
Check for dynamic code execution functionsExamine the plugin source code in the widget-wrangler plugin folder for the presence of eval(), extract(), assert(), preg_replace() with /e modifier, create_function(), or similar functions that execute dynamically generated codeAffected if Any of these functions are present and process user-supplied input without sanitization
-
Verify plugin is accessible without authenticationConfirm the WordPress site allows access to Widget Wrangler functionality for non-logged-in visitors; check plugin settings and widget display configurationsAffected if The plugin or its widgets can be accessed or rendered by unauthenticated users (required for the 9.1 CVSS rating exploit)
You are affected if the Widget Wrangler plugin is installed with any version through 2.3.9 and contains dynamic code execution functions accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Widget Wrangler to the latest patched version immediately. If no patched version is available, disable or remove the plugin until a fix is released. Review the site for any signs of compromise.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25447 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25447 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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