LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25447: WordPress Widget Wrangler plugin <= 2.3.9 - Remote Code Execution (RCE) vulnerability

Improper 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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25447 is a critical code injection issue in the WordPress Widget Wrangler plugin through version 2.3.9. If abused, it could let a highly privileged authenticated user execute code and fully compromise the site. There is no provided evidence of active exploitation.

Executive priority

Treat as high-priority for any site using this plugin, especially public-facing or revenue-impacting WordPress properties. Prioritize inventory and remediation, but avoid assuming mass exploitation from the provided evidence.

Technical view

The CVE describes CWE-94 improper control of code generation in Jonathan Daggerhart Widget Wrangler. CVSS 3.1 is 9.1: network exploitable, low complexity, high privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the Widget Wrangler plugin at version 2.3.9 or earlier. The CVSS vector indicates exploitation requires high privileges, reducing broad internet drive-by risk but raising concern for compromised admin accounts or malicious insiders.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public details identify remote code execution/code injection, but no safe, source-grounded exploit conditions beyond the CVSS vector are available here.

Researcher notes

Key gap: sources do not provide patch version, exploit proof, or detailed vulnerable code path. Analysis should stay anchored to CVE metadata and Patchstack’s advisory entry. Validate plugin presence and version before escalating incident response.

Mitigation direction

  • Inventory WordPress sites for the Widget Wrangler plugin.
  • Identify installations running Widget Wrangler 2.3.9 or earlier.
  • Check vendor, WordPress.org, and Patchstack guidance for fixed versions or advisories.
  • Disable or remove the plugin where business use is not required.
  • Limit WordPress administrator access to trusted, MFA-protected accounts.
  • Review recent administrator activity for unexpected plugin or widget changes.

Validation and detection

  • Confirm whether Widget Wrangler is installed and active on each WordPress site.
  • Record the installed plugin version and compare against affected versions through 2.3.9.
  • Verify remediation status after update, removal, or disablement.
  • Review access logs and admin audit logs for suspicious high-privilege activity.
  • Confirm privileged WordPress accounts use MFA and least privilege.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25447 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-25447Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jonathan DaggerhartWidget Wranglerwidget-wrangler, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.