dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-8105

HIGH · 7.3 CVSS v3.1 Published 2025-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The The Soledad theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 8.6.7. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Soledad theme for WordPress fails to validate user input before passing it to the do_shortcode() function, allowing unauthenticated attackers to inject and execute arbitrary shortcodes. Since shortcodes can trigger various plugin/theme functionalities including potentially dangerous PHP execution paths, this enables severe attacks without authentication.

MitigationUpdate the Soledad theme to a version newer than 8.6.7. If immediate updating is not possible, implement web application firewall rules to block requests containing shortcode patterns or temporarily switch to a secure alternative theme.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Soledad theme is installed
    Navigate to wp-content/themes/ in your WordPress installation directory and verify the soledad folder exists
    Affected if The soledad folder exists in the themes directory
  2. Check if Soledad theme is active
    Log into WordPress admin panel, go to Appearance > Themes, and note whether Soledad is the currently active theme
    Affected if Soledad theme is activated on the site
  3. Determine installed Soledad version
    Open wp-content/themes/soledad/style.css and locate the 'Version:' header in the theme comment block at the top of the file
    Affected if The version displayed is 8.6.7 or lower
  4. Compare version to fixed release
    Compare the version found in step 3 against version 8.6.7 - any version greater than 8.6.7 contains the fix
    Affected if Installed version is 8.6.7 or lower, meaning the vulnerability is present in the theme code
  5. Verify shortcode processing exposure
    Review theme PHP files (particularly functions.php and any custom shortcode handlers) for instances where user-supplied input is passed directly to do_shortcode() without sanitization
    Affected if The theme code contains unsanitized do_shortcode() calls processing user input

If Soledad theme is active and the installed version is 8.6.7 or lower, the environment is vulnerable to unauthenticated shortcode injection attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Soledad theme to a version newer than 8.6.7. If immediate updating is not possible, implement web application firewall rules to block requests containing shortcode patterns or temporarily switch to a secure alternative theme.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8105 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data