Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as contributor or higher
-
ExploitSubmit [siteorigin_widget] shortcode with traversal path in JSON instance
-
ExecutionBypass sanitize_field_input via direct widget() call to get_instance_css
-
ImpactRead arbitrary server file contents (e.g. wp-config.php)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account at contributor level or above on a site with SiteOrigin Widgets Bundle ≤1.74.3 installed and active, and the ability to use the [siteorigin_widget] shortcode (available to contributors by default). The specific technical condition is that the shortcode handler in base/inc/shortcode.php calls $the_widget->widget() directly on the attacker-controlled decoded JSON instance, bypassing the update()/sanitize_field_input() hex-color validation that normally guards get_instance_css. Limiting factors: exploitation is gated on obtaining a contributor+ account (most impactful where open user registration or many low-trust authors exist), it yields read-only file disclosure (no write/RCE directly), and it requires no user interaction (UI:N). |
| Impact | This is a credible but moderate-priority issue, not a top-tier emergency. The CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) reflects a remotely reachable, low-complexity arbitrary file read, but the PR:L requirement (contributor-level account and above) is the dominant limiting factor - this is not an unauthenticated flaw. Impact is confidentiality-only (C:H, I:N, A:N): an attacker can read sensitive files such as wp-config.php (database credentials, auth salts) but cannot directly modify data or cause denial of service, though disclosed credentials could enable follow-on compromise. No EPSS score, KEV listing, or POC indicator was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the finding originates from Wordfence threat intelligence research rather than incident response. No signals conflict here: the CVSS vector, the description (contributor-level authenticated access), and the referenced source code all consistently point to an authenticated, network-reachable confidentiality flaw. The realistic risk is elevated on sites that allow contributor self-registration or have many low-trust authors, and low on tightly controlled single-author sites. |
| Exploit ScenarioDerived | An attacker who holds (or registers for) a contributor-level WordPress account on a site running SiteOrigin Widgets Bundle ≤1.74.3 submits a [siteorigin_widget] shortcode whose decoded JSON instance carries a directory-traversal path in a field expected to hold a CSS/color value. Because the shortcode handler invokes the widget's widget() method directly on the attacker-supplied instance, the normal update()/sanitize_field_input() validation that would reject the malformed value is bypassed, and get_instance_css reads an arbitrary file (e.g. wp-config.php) whose contents are exposed. No public exploit was identified at time of analysis, and low attack complexity (AC:L) means the request requires no special timing or race conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Authenticated directory traversal in the SiteOrigin Widgets Bundle WordPress plugin (all versions up to and including 1.74.3) allows contributor-level users and above to read arbitrary files on the server through the get_instance_css function, exposing sensitive data such as wp-config.php secrets. Exploitation requires only a low-privilege contributor account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), needs no user interaction, and is limited to read-only information disclosure with no direct write or code-execution impact; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited. Overall this is a credible but moderate-priority issue rather than a top-tier emergency, with risk concentrated on sites that grant contributor access broadly.
RemediationAI
Patch status: Upstream fix available (PR/commit); released patched version not independently confirmed - the referenced compare (540f834469fe...bf80892709fb) and Trac changeset 3724795 show the corrected code in trunk, so administrators should update the plugin as soon as the vendor publishes the fixed release and confirm the exact version against the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/500f18e6-14ca-4632-9317-5886fa2bb763?source=cve). Until a tagged fix is installed, the most effective control is to remove the attack precondition: disable or deactivate the SiteOrigin Widgets Bundle plugin if its widgets are not required (loses all bundled widget functionality), or, if it must stay active, stop low-trust users from reaching the [siteorigin_widget] shortcode by downgrading untrusted accounts below contributor level and closing open/unmoderated registration - the trade-off is that any legitimate contributor who needs the shortcode will no longer be able to render those widgets. Audit existing contributor-and-above accounts for unknown or stale users and rotate any server-side secrets (database credentials, salts and API keys) that could have been exposed in wp-config.php or similar readable files. Because the request is authenticated and uses a legitimate shortcode, generic WAF or blocking rules are unlikely to reliably distinguish malicious from benign traffic and should not be relied on as the primary mitigation.
Affected VersionsENISA
Affected Packages
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
This is a CWE-22 path traversal in a WordPress plugin, rooted in an ordering and validation gap rather than a raw sanitization failure. The plugin's normal instance field handling pipeline (update() and sanitize_field_input()) would reject non-hex color values that could contain traversal sequences before they reach CSS generation. However, the [siteorigin_widget] shortcode handler in base/inc/shortcode.php (around lines 31 and 51) instantiates the widget from an attacker-supplied decoded JSON instance and calls $the_widget->widget() directly, skipping that pipeline entirely. The unvalidated instance data then flows into get_instance_css() (base/siteorigin-widget.class.php, particularly lines 1006, 1117, 1134 and 1148 in 1.74.3), where a file path derived from the controlled field is used without proper restriction, permitting relative traversal sequences to escape the intended directory. Affected software is identified by CPE cpe:2.3:a:gpriday:siteorigin_widgets_bundle:*:*:*:*:*:*:*:*, covering all builds through the vulnerable 1.74.3 tag. Because the shortcode is available to contributor-level users by default, the bypass of the update()/sanitize_field_input() guard converts a low-privilege content-editing capability into a server-side file-read primitive.
Know when Siteorigin Widgets Bundle 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
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network-reachable via shortcode with low complexity (AV:N/AC:L), requires a contributor-level account so PR:L, no user interaction, and arbitrary file read yields C:H with no integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.74.3 via the get_instance_css function. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information. The widget's normal update()/sanitize_field_input() pipeline - which would reject non-hex color values - is bypassed entirely because the [siteorigin_widget] shortcode handler calls $the_widget->widget() directly on the attacker-supplied decoded JSON instance.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Siteorigin Widgets Bundle
View allThe SiteOrigin Widgets Bundle WordPress plugin before 1.51.0 does not validate user input before using it to generate pa
Local file inclusion in the SiteOrigin Widgets Bundle WordPress plugin, in all versions up to and including 1.73.2, lets
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'siteor
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's SiteOri
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters i
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the code editor in a
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the onclick paramete
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the features attribu
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `data-url` DOM E
The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Image Grid widge
Missing Authorization vulnerability in Greg - SiteOrigin SiteOrigin Widgets Bundle so-widgets-bundle allows Exploiting I
EUVD-2026-96222
GHSA-2v8j-3m7w-9w5f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB