dbcve.org
SoledadWordPress extension · Pencidesign

CVE-2024-31367

HIGH · 7.1 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 8.4.6 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
Missing Authorization vulnerability in PenciDesign Soledad.This issue affects Soledad: from n/a through 8.4.2.

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

Missing Authorization (broken access control) vulnerability in the Soledad WordPress theme from PenciDesign. The theme fails to properly verify user permissions before allowing access to certain functionality or resources, potentially allowing authenticated attackers to perform actions beyond their authorized privileges. The CVSS 7.1 score indicates high severity due to network exploitability and moderate attack complexity.

MitigationUpdate Soledad theme to the latest version containing the security patch. If no update is available, conduct a code review to identify and add proper capability checks, nonce verification, and permission validation before executing privileged operations.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SoledadWordPress extension
Affected:< 8.4.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

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 the Soledad theme version
    In WordPress admin dashboard, go to Appearance > Themes. Find the Soledad theme and click on it to view the theme details. The version number is displayed there. Alternatively, check the style.css file in wp-content/themes/soledad/ and look for the 'Version:' comment in the file header.
    Affected if The version displayed is lower than 8.4.6 (for example, 8.4.5, 8.4.0, or any version number starting with a digit lower than 8 in the major version position)
  2. Check theme files for version constant
    If you have file system access, open the file functions.php or inc/theme-functions.php within the Soledad theme directory (wp-content/themes/soledad/). Look for a variable defining the theme version, often named $theme_version, SOLEDIA_THEME_VERSION, or similar. Note the value assigned to it.
    Affected if The version constant or variable shows a number less than 8.4.6
  3. Verify WordPress user roles exist
    In WordPress admin, go to Users > All Users. Review the list of registered users and their assigned roles (Administrator, Editor, Author, Contributor, Subscriber). This vulnerability affects authenticated users, so having multiple user accounts with different roles increases the potential attack surface.
    Affected if There are multiple user accounts with roles beyond Subscriber, particularly if any role has access to theme-specific features or settings
  4. Check for exposed theme endpoints
    If you have access to server logs or can test HTTP requests, look for AJAX endpoints or admin-ajax.php calls that the Soledad theme registers. Inspect the theme's inc/ folder for PHP files handling AJAX actions (search for add_action("wp_ajax_...) or add_action("wp_ajax_nopriv_...)). Note which actions do not include capability checks like current_user_can() before performing operations.
    Affected if Theme AJAX handlers exist that lack current_user_can() or similar permission checks before executing privileged operations

You are affected if your installed Soledad theme version is lower than 8.4.6 and you have authenticated user accounts with privileges beyond subscriber level.

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
Upgrade available Upgrade to 8.4.6 or later
Fixed in 8.4.6
Interim mitigation

Update Soledad theme to the latest version containing the security patch. If no update is available, conduct a code review to identify and add proper capability checks, nonce verification, and permission validation before executing privileged operations.

Recommended fix Moderate confidence

8.4.6 or latest version of Soledad theme

  1. Back up your website database and files before making any changes
  2. Update the Soledad theme to version 8.4.6 or the latest available version
  3. Verify the update was successful by checking the theme version in WordPress admin
  4. Confirm the vulnerability is resolved by testing affected functionality
Caveat Review the theme changelog before upgrading to check for any breaking changes or template modifications

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

Fix this in Soledad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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