Skip to main content

Widget Options EUVDEUVD-2026-114309

| CVE-2026-116852 CRITICAL
Code Injection (CWE-94)
2026-10-30 Patchstack GHSA-pqqr-8pmv-5qrf
9.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with privileged WordPress account
  2. Delivery
    Access Widget Options plugin function
  3. Exploit
    Inject malicious code (CWE-94)
  4. Execution
    Execute arbitrary code on web server
  5. Impact
    Full compromise of site and host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated account on a target WordPress site running the Widget Options plugin version 4.2.5 or earlier (vendor marketing_fire). The title indicates an Author-level role suffices, though the supplied CVSS sets PR:H - the exact required privilege should be confirmed with Patchstack. Limiting factors: a valid authenticated account is mandatory (PR is not None), so the site must expose account provisioning (e.g. open user registration) or the attacker must already possess credentials; sites not running Widget Options, or running a version above 4.2.5, are unaffected. No user interaction is required (UI:N). The specific plugin feature, parameter, or configuration that triggers the code injection is not described in the available sources.

Impact

This is a genuine high-priority issue, corroborated by multiple signals pointing the same direction: the vuln.today decision label is act_now, the CVSS base score is 9.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H - network vector, low complexity, no user interaction, scope-changing total C/I/A loss), and the flaw is CWE-94 code injection yielding remote code execution, which is among the most impactful outcomes for a web application. Countervailing factors temper the urgency: no EPSS score was supplied, the CVE is not listed in CISA KEV, and no proof-of-concept or working exploit was provided - only a Patchstack advisory reference - so there is no evidence of active or at-scale exploitation at this time. One internal inconsistency should be verified with the vendor: the title explicitly describes an 'Author' Remote Code Execution, implying a relatively low-privileged authenticated WordPress role, yet the supplied CVSS vector sets PR:H (high privilege); the required privilege level materially changes real-world exploitability, so reconcile the 'Author' wording against PR:H with Patchstack before finalizing prioritization. Net: treat as act_now for remediation given RCE + act_now label, but note the realistic barrier is that an attacker must already hold a valid authenticated account on the target site.

Exploit ScenarioDerived

An attacker who holds (or obtains, e.g. via open registration or credential compromise) an authenticated WordPress account with the required privilege level on a site running Widget Options <= 4.2.5 abuses the plugin to inject code that the server executes, achieving remote code execution. Because the CVSS vector is AV:N/AC:L/UI:N with scope change, exploitation is remote, low-complexity, and requires no victim interaction once the account exists. No verified public exploit code was provided in the input, only a Patchstack advisory reference.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 30, 2026

Remote code execution in the WordPress Widget Options plugin through version 4.2.5 allows authenticated attackers to inject and execute code on vulnerable sites, with the supplied CVSS vector indicating high privileges while the advisory title indicates an Author-level account may suffice. The flaw is network-reachable, low-complexity, requires no user interaction, and is scope-changing with high confidentiality, integrity, and availability impact. No public exploit code or CISA KEV entry was identified in the supplied data; the vuln.today decision label is act_now, so prioritize confirming the exact required role and applying a fix or removing the plugin.

RemediationAI

Patch status: No vendor-released patch identified at time of analysis, and no fixed version is listed; confirm the corrected release with Marketing Fire/Patchstack before upgrading beyond 4.2.5. Until a fix is available, the specific compensating control is to disable or remove the Widget Options plugin from affected WordPress sites, accepting that widget configuration and layout features will stop working. Because exploitation requires an authenticated account, also restrict account provisioning (for example, close open registration) and audit or reduce Author-and-above accounts; these controls lower exposure but do not replace a vendor patch. Monitor the Patchstack advisory for update details at https://patchstack.com/database/wordpress/plugin/widget-options/vulnerability/wordpress-widget-options-plugin-4-2-5-remote-code-execution-rce-vulnerability?_s_id=cve.

Affected VersionsENISA

Widget Options n/a ≤4.2.5

Affected Packages

euvd widget_options no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CVE-2026-116852 is a CWE-94 code injection in Marketing Fire's Widget Options WordPress plugin, affecting releases up to and including 4.2.5 (CPE cpe:2.3:a:marketing_fire:widget_options). The supplied CVSS vector describes network access, low attack complexity, no user interaction, scope change, and total confidentiality, integrity, and availability impact, but it sets PR:H while the advisory title says Author; the exact minimum role is therefore unresolved and should be confirmed with Patchstack. Exploitation requires a valid authenticated account on a site running the vulnerable plugin; the specific plugin feature, parameter, or configuration that permits code injection is not described in the available sources. Sites without the plugin or running a later version are not affected by this CVE.

Know when Widget Options gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Title states 'Author' RCE, a low-privileged authenticated role, so PR:L rather than the input's PR:H; network, low-complexity, no interaction, with code execution escaping the app (S:C) and full C/I/A loss.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Author Remote Code Execution (RCE) in Widget Options <= 4.2.5 versions.

Executive ViewAI

Why It Matters

A critical remote code execution vulnerability in the WordPress Widget Options plugin (through version 4.2.5) enables attackers with authenticated access-potentially as low as Author-level-to inject and execute arbitrary code on vulnerable sites, threatening full compromise of confidentiality, integrity, and availability. Leadership should care because any compromise of a WordPress site can expose sensitive data, disrupt services, and damage brand trust, with potential regulatory and reputational consequences.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: removing or disabling the Widget Options plugin on affected sites; restricting authenticated access to trusted users and reviewing user roles to eliminate unnecessary Author-level permissions; deploying a web application firewall (WAF) with virtual patching rules if available; and enabling enhanced monitoring and logging of plugin and administrative activities to detect exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.6%
Top 52% exploitable
Prevalence
Medium
popular WordPress plugin, broad but not universal install base
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy