Skip to main content
Menu
CVEs

CVE

Soledad unauthenticated code execution in more-post AJAX handler

CVE-2026-121684EUVD-2026-126911GHSA-8PJX-RJJ7-F4JGNeeds attention

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

8.1HighCNA
Exploited
Public exploit code, no confirmed attacks
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
First public exploit on GitHub Nov 17
Last checked
0.43% · 38th percentile
52/100 · provisional
1 proof of concept on GitHub

Summary

The Soledad WordPress theme from pencidesign has a flaw that lets an unauthenticated attacker run arbitrary code on the affected site. The attacker can exploit it remotely over the network by sending a crafted web request, without logging in.

Written by a model from the sources below. Verify against them.

Original description

The Soledad theme for WordPress is vulnerable to unauthenticated Remote Code Execution in versions up to, and including, 8.7.7 The public penci_more_post_ajax AJAX action feeds infeedads[ads_code] (base64+urldecoded) to penci_safe_shortcode(), whose allowlist regex inspects only the hyphen-truncated outer shortcode name (e.g. 'adinserter') and never the nested [elementor-element k=.. data=..] tag, so do_shortcode() renders an attacker-chosen Elementor element. The rendered penci-featured-sliders widget passes its unsanitized 'style' setting to include dirname(__FILE__)."/{$style}.php", a path-traversal local file inclusion.

cve.now Index

52Pcve.now Index 52 of 100 · methodology v3 · provisional
  • Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.1/10CVSS 8.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 57 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121684 (Soledad - Multi-Concept Blog/Magazine WordPress Theme <= 8.7.7 - Unauthenticated Remote Code Execution via penci_more_post_ajax…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121684 (entry last updated 2026-11-17):
Affected:
- pencidesign Soledad: through 8.7.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121684 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121684 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bb3fe92d-adf8-4ab7-bc1a-9cf78ea4412f?source=cve
- https://themeforest.net/item/soledad-multiconcept-blogmagazine-wp-theme/12945398
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121684
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121684"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Exploit code on GitHub

    im0xfay/CVE-2026-121684

Affected versions

  • pencidesign Soledad

    through 8.7.7

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-121684

Is CVE-2026-121684 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data

Which versions are affected by CVE-2026-121684?

Soledad: through 8.7.7.Source: cve.now feed data

More CVEs