Introduction
A public "load more posts" AJAX handler in the Soledad WordPress theme can be driven, without any login, into rendering an attacker-chosen Elementor widget that feeds a PHP include, a chain Wordfence classifies as unauthenticated remote code execution. Because the handler is reachable by anonymous visitors on every affected site, any deployment still running Soledad 8.7.7 or earlier has a documented reason to move to 8.7.8.
Soledad is a commercial multipurpose WordPress theme from PenciDesign, aimed at blogs, news and magazine sites, business sites, creators and WooCommerce stores. Its ThemeForest listing displays 60,496 purchases, PenciDesign advertises 60,000+ sales, and ThemeForest lists the vendor as a Power Elite Author since June 2015. Those numbers reflect commercial reach rather than a count of vulnerable or internet-exposed installations, but they explain why a theme-level flaw like this one touches a broad slice of WordPress publishing.
Key facts
- CVE: CVE-2026-121684
- Severity: CVSS 3.1 base score 8.1 (High), vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by Wordfence as CNA. NVD reproduces the CNA score and has not published an independent NVD score. - Weakness: CWE-74, improper neutralization of special elements in output used by a downstream component
- Affected: Soledad theme for WordPress, versions up to and including 8.7.7
- Fixed: 8.7.8 (released October 30, 2026)
- Credited researcher: Bill Hsu of CertiK
- Exploitation status: not publicly confirmed in the examined sources
Technical Information
Root cause: the allowlist inspects one thing, the renderer executes another
The core problem is a mismatch between what a validation function examines and what the downstream component actually processes. Soledad routes attacker-supplied shortcode markup through a filter, penci_safe_shortcode(), before calling WordPress's do_shortcode(). The filter's allowlist regex looks only at the outer shortcode name, and only up to the first hyphen. The advisory's example of an accepted outer name is adinserter.
do_shortcode() does not share that narrow view. It processes the entire string, nested tags included. So an allowed outer shortcode can wrap a nested Elementor tag that the filter never looks at:
[elementor-element k=.. data=..]
That nested tag lets the attacker select which Elementor element gets rendered. In the advisory, the element that escalates the bug is the penci-featured-sliders widget.
The file inclusion sink
The penci-featured-sliders widget takes its style setting and places it, unsanitized, directly into a PHP include. The expression published in the advisory is:
include dirname(__FILE__)."/{$style}.php"
Because style is attacker influenced through the Elementor element data, path traversal sequences in that value move the include outside the widget's directory. The sink always appends .php, so the inclusion targets PHP files. Wordfence describes the result as path traversal local file inclusion and classifies the overall chain as remote code execution.
Attack flow as described in the advisory
The public description lays out four stages. We present them as documented. The advisory does not publish a complete working payload, and we are not reconstructing one.
- Public entry point. An unauthenticated request reaches the WordPress AJAX endpoint with
action=penci_more_post_ajax. VulDB notes these are crafted HTTP POST requests. - Encoded carrier. The payload sits in
infeedads[ads_code]. The theme base64 decodes and URL decodes it, then passes it topenci_safe_shortcode(). - Allowlist bypass. The decoded value is a nested shortcode: an outer name that passes the hyphen-truncated regex check wraps an inner
[elementor-element k=.. data=..]tag. The filter approves the outer name, anddo_shortcode()renders the attacker-chosen Elementor element. - Local file inclusion. The rendered
penci-featured-sliderswidget passes itsstylesetting intoinclude dirname(__FILE__)."/{$style}.php", where traversal sequences redirect the include.
VulDB describes the practical impact as reading sensitive files such as wp-config.php through the inclusion, and possibly reaching code execution by pairing the inclusion with a PHP file placed on disk by other means.
Reading the CVSS vector carefully
The vector combines no required privileges and no user interaction with High attack complexity. FIRST's CVSS v3.1 specification defines high complexity as depending on conditions beyond the attacker's control that require measurable preparation or execution effort. The Soledad advisory does not identify which condition drives that rating, and it does not specify minimum Elementor requirements or filesystem prerequisites. We leave those as unknowns rather than borrowing conditions from older Soledad bugs, such as the Windows-only limitation of CVE-2024-11289.
In practice, authentication is not a barrier, but the score does not claim that every affected site is trivially exploitable. Equally, a CVSS base score describes intrinsic severity, not observed attacks.
Exploitation status
The examined sources do not confirm exploitation in the wild, named victims, campaigns or threat actors. TheHackerWire reports that no public PoC has been confirmed and that the CVE is not in CISA KEV. The CISA catalog material retrieved for our briefing (catalog version 2026.11.13) was truncated, so we do not treat it as independent proof of absence. No hashes, attacking IP addresses, filenames or malicious domains have been published.
Patch Information
The fix is Soledad 8.7.8. All advisory sources we checked agree on the boundary: every build up to and including 8.7.7 is vulnerable, and 8.7.8 is the first fixed release. Wordfence, the CNA, lists the issue as "Patched? Yes" and advises users to "Update to version 8.7.8, or a newer patched version". Patchstack separately lists 8.7.8 as the version containing the fix. NVD's record points to both the Wordfence advisory and the PenciDesign ThemeForest product page, which is where the update is distributed.
What the vendor published
PenciDesign released 8.7.8 on October 30, 2026, about two and a half weeks before the CVE went public on November 16, 2026. The changelog does not mention penci_more_post_ajax, penci_safe_shortcode() or the featured sliders widget by name. The only security entry is general:
Improve: "Addressed all identified security issues."
The remaining 8.7.8 entries cover the dashboard UI, Header Builder fixes, schema fixes, a new optional MCP plugin and updated bundled plugins. Soledad is a paid ThemeForest theme with no public source repository, so there is no public commit, diff or code snippet for this fix. The fix can be confirmed by version number only, not by code.
What a sound fix needs to break
The chain has two independent weaknesses: the allowlist bypass at the entry point and the unsanitized include in the widget. In our analysis, a robust fix would do one or more of the following:
- stop accepting shortcode markup from unauthenticated AJAX input entirely
- compare the complete shortcode tag name exactly, instead of a hyphen-truncated prefix
- reject or strip nested shortcodes before rendering
- restrict the slider's
stylevalue to a fixed list of known template names, or pass it throughsanitize_file_name()orbasename()before theinclude
Any of the first three closes the entry point. The last removes the file inclusion step in every code path that reaches the widget. This list is our own analysis of what a sound fix looks like, not a description of the vendor's code. Public sources do not tell us whether 8.7.8 fixed one link of the chain or both.
Why the vague changelog matters
The 8.7.7 changelog also said "various security issues" had been fixed, yet this chain was still exploitable in that version. A filter like penci_safe_shortcode() is the kind of control usually added after earlier shortcode bugs, and here the attacker gets around the filter rather than finding the endpoint wide open. That is our inference, not something the vendor has confirmed. For defenders, the takeaway is that the version number is the only verifiable proof of remediation.
Getting and verifying the patched build
- 8.7.8 is available as a normal theme update through ThemeForest/Envato.
- Since 8.7.5, licensed users can also update directly from the Soledad update server.
- For Soledad 5.2 and later, PenciDesign's procedure is: Appearance > Themes > Update Now, then Appearance > Install Plugins to update the bundled plugins in use. If a child theme is active, update the parent theme.
- Updating replaces theme files, so direct file modifications are lost. The vendor advises recording them so they can be reapplied, and states that Customizer data, posts, pages and widgets are unaffected.
- Installations below 5.2 need the vendor's manual process: download the ThemeForest package, extract
soledad.zip, activate another theme, delete the old Soledad theme and reinstall through the theme upload interface. - To confirm a site is fixed, check that the
Version:line in the Soledadstyle.css(or the version shown under Appearance > Themes) reads 8.7.8 or later.
No CVE-specific configuration workaround or manual code patch has been published as a substitute for upgrading.
Detection Methods
There is currently no vendor-validated, exploit-specific public signature for CVE-2026-121684: no YARA, Suricata or Snort rules, no confirmed Nuclei template, and no campaign IoCs. Detection depends on understanding the request shape well enough to hunt for it, plus managed WAF coverage.
1. Exposure detection through version inventory
Wordfence and Patchstack both list Soledad 8.7.7 and earlier as vulnerable and 8.7.8 as fixed. Wordfence's Intelligence vulnerability API is free to query and can be fed into an asset inventory or vulnerability scanning pipeline to flag WordPress sites still on a vulnerable build. This identifies exposure, not compromise.
2. What each stage of the chain leaves behind
- Entry point: an unauthenticated POST to
admin-ajax.phpwithaction=penci_more_post_ajax. - Carrier parameter: the payload in
infeedads[ads_code], base64 and URL encoded. - Allowlist bypass: after decoding, a nested shortcode in which an allowed outer name (the advisory's example is
adinserter) wraps an inner[elementor-element k=.. data=..]tag. - LFI sink: the inner element renders
penci-featured-sliders, and a maliciousstylevalue carries path traversal sequences.
3. Network and WAF hunting: decode before you match
The dangerous strings are encoded. A WAF rule or log search that matches ../ or elementor-element against the raw POST body will probably miss the attack, because those strings only appear after base64 and URL decoding. A useful hunt should:
- Select POSTs to
admin-ajax.phpwhereaction=penci_more_post_ajax, from clients without a WordPress session cookie. - Extract
infeedads[ads_code]and apply the same decoding the theme does: base64, then URL decoding. - Alert on decoded content containing a nested
[elementor-elementtag, references topenci-featured-sliders, or directory traversal sequences in astylevalue.
penci_more_post_ajax is a legitimate front-end "load more posts" handler, so the action name alone is noisy. Baseline normal usage and treat the presence and decoded content of ads_code as the strong signal. VulDB's guidance aligns with this, recommending WAF rules that catch nested shortcodes containing Elementor tags, or traversal sequences, in parameters sent to WordPress handlers.
4. Commercial and virtual patch coverage
Patchstack states it has issued a mitigation rule that blocks attacks until the site is updated. The rule logic is proprietary, so it is usable only as a managed control, not as a reproducible signature.
5. Caution about generic toolkit templates
TheHackerWire's CVE page provides a Sigma rule, a Splunk query, a Nuclei command and a ModSecurity rule, labelled by the site itself as "Generic detection templates, tune before production". Review them before use:
- Sigma rule: selects only on HTTP 500/502 status codes, and its condition references an
indicators*selection that is never defined, so it is incomplete as written. - Splunk query: searches for literal strings such as "Affected Software" and the CVE ID, which will not appear in attack traffic.
- ModSecurity rule: matches tokens such as
../against raw arguments, which runs straight into the encoding problem above. - Nuclei command: references a template by CVE ID. We could not confirm that such a template exists.
Treat these as starting points to adapt with the decoding logic above, not as working detections.
6. Host-side and post-exploitation signals
Based on the bug class and the .php suffix appended by the sink, reasonable places to hunt on hosts running Soledad 8.7.7 or earlier include:
- PHP include warnings or errors referencing the theme's featured sliders widget path, especially with traversal in the path.
- Unexpected
.phpfiles in writable locations such as uploads directories. - Signs of database credential misuse following suspicious
penci_more_post_ajaxactivity.
Correlate host signals with the decoded payload network hunt to distinguish probes from successful exploitation.
Affected Systems and Versions
- Product: Soledad (Multi Concept Blog/Magazine WordPress theme) by PenciDesign
- Vulnerable: all versions up to and including 8.7.7
- Fixed: 8.7.8 and later patched releases
- Vulnerable path: the unauthenticated
penci_more_post_ajaxAJAX action,penci_safe_shortcode(), Elementor element rendering viado_shortcode(), and thepenci-featured-sliderswidget'sstylesetting - Child theme deployments: remain exposed until the parent Soledad theme is updated
- Unspecified conditions: the advisory does not state minimum Elementor versions, operating system restrictions or filesystem prerequisites, and does not identify the specific condition behind the High attack complexity rating
The separate Penci Soledad Data Migrator plugin issue (CVE-2024-3551) is a distinct vulnerability and is not part of this CVE's affected range.
Vendor Security History
Soledad has several prior disclosures that touch the same attack surfaces. They are distinct issues and should not be merged into one affected range.
- CVE-2025-8105: Soledad through 8.6.7, unauthenticated arbitrary shortcode execution caused by insufficient validation before
do_shortcode(), CVSS 7.3 with low attack complexity. Fixed in 8.6.8. This is the closest analogue: both involve unauthenticated shortcode processing, but the current issue is an allowlist bypass leading to a widget file inclusion, and the fixed versions differ. - CVE-2024-11289: Soledad through 8.5.9, unauthenticated limited local file inclusion through several AJAX functions, exploitable only on Windows, CVSS 8.1. The examined CVE record does not state a fixed version.
- CVE-2024-3551: Penci Soledad Data Migrator plugin through 1.3.0, unauthenticated local file inclusion via the
dataparameter with conditional code execution, CVSS 9.8. The examined record does not state a fixed version. - Additional LFI issues: CVE-2025-8142, CVE-2025-59588 and CVE-2025-68066 are also recorded against Soledad.
This history shows that shortcode handling and file inclusion recur as security-relevant surfaces in the theme. It does not establish that an earlier patch caused the current flaw or that the issues share an implementation. PenciDesign's changelog does show ongoing security maintenance, including the 8.7.8 release, and its FAQ states that theme updates with security fixes continue after a customer's support period expires.
References
- NVD: CVE-2026-121684
- CVE.org record: CVE-2026-121684
- Wordfence advisory: Soledad 8.7.7 and earlier, Unauthenticated Remote Code Execution via penci_more_post_ajax
- Patchstack: Soledad theme 8.7.7 unauthenticated remote code execution
- Soledad on ThemeForest (update distribution)
- VulDB: CVE-2026-121684
- TheHackerWire: CVE-2026-121684
- BugShield: Soledad CVE-2026-121684
- PenciDesign: Soledad changelog
- PenciDesign Ticksy: Soledad update changelog
- PenciDesign Ticksy: How to update Soledad theme to latest version
- PenciDesign: Soledad FAQ
- PenciDesign: Soledad plugins
- PenciDesign: Soledad product site
- PenciDesign profile on ThemeForest
- Wordfence: Soledad 8.6.7 and earlier, Unauthenticated Arbitrary Shortcode Execution (CVE-2025-8105)
- CVE.org record: CVE-2024-11289
- CVE.org record: CVE-2024-3551
- CISA Known Exploited Vulnerabilities feed
- FIRST: CVSS v3.1 Specification Document



