dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-64188

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Incorrect Privilege Assignment vulnerability in PenciDesign Soledad soledad allows Privilege Escalation.This issue affects Soledad: from n/a through <= 8.6.9.

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 · moderate confidence

The Soledad WordPress theme through version 8.6.9 contains an Incorrect Privilege Assignment vulnerability that allows authenticated users to escalate their privileges, potentially achieving administrative access. The CVSS 9.8 rating indicates this can likely be exploited with minimal user authentication.

MitigationUpdate Soledad theme to the latest patched version immediately. If no patched version is available, consider alternative theme options or implement additional access controls while awaiting a vendor fix.

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
High
Integrity
High
Availability
High

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

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. Locate Soledad theme installation
    Check if the Soledad theme files exist in your WordPress installation under wp-content/themes/soledad/ or wp-content/themes/puai-soledad/
    Affected if The theme directory exists in your WordPress themes folder
  2. Identify Soledad theme version
    Open the style.css file within the Soledad theme folder and look for the 'Version:' declaration in the file header, or check the theme's main functions.php file for a version constant
    Affected if The version number is 8.6.9 or lower (any version up to and including 8.6.9)
  3. Verify user account existence
    Check your WordPress database users table (wp_users) or log in to wp-admin and navigate to Users > All Users to see if any user accounts exist beyond the administrator account
    Affected if There is at least one additional user account registered on the WordPress site (any role including subscriber)
  4. Confirm user registration status
    In WordPress admin, go to Settings > General and check if 'Anyone can register' is enabled, or check the wp_options table for option_name 'users_can_register' set to 1
    Affected if User registration is enabled, allowing new accounts to be created

Your environment is affected if the Soledad theme is installed with a version of 8.6.9 or lower AND your WordPress site has at least one registered user account (or allows user registration), providing an authenticated user who could exploit the privilege escalation flaw.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Soledad theme to the latest patched version immediately. If no patched version is available, consider alternative theme options or implement additional access controls while awaiting a vendor fix.

Recommended fix Moderate confidence

Latest version of Soledad theme (version > 8.6.9) from PenciDesign official sources

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Soledad theme in the installed themes list
  4. 4. Click on the Soledad theme to view its details
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version of the Soledad theme from the official PenciDesign source (themeforest.net or pencidesign.com)
  7. 7. Upload and install the updated theme through WordPress admin or via FTP
  8. 8. After updating, verify that the privilege escalation vulnerability is resolved by testing user role capabilities
Caveat Review theme settings and customizations after upgrade as template changes may affect site appearance

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64188 — 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-64188 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