dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-11289

HIGH · 8.1 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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
The Soledad theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 8.5.9 via several functions like penci_archive_more_post_ajax_func, penci_more_post_ajax_func, and penci_more_featured_post_ajax_func. This makes it possible for unauthenticated attackers to include and execute PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where PHP files can be uploaded and included. The exploitability of this is limited to Windows.

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 WordPress theme versions up to 8.5.9 contain a Local File Inclusion (LFI) vulnerability in multiple AJAX functions (penci_archive_more_post_ajax_func, penci_more_post_ajax_func, and penci_more_featured_post_ajax_func). Unauthenticated attackers can manipulate the include mechanism to execute arbitrary PHP code on Windows servers.

MitigationUpdate the Soledad theme to the latest version (8.5.10 or later) which should contain the patch for this LFI vulnerability. If immediate updating is not possible, consider disabling the affected AJAX endpoints via web server configuration or .htaccess rules to block path traversal attempts.

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

CVSS:3.1/AV:N/AC:H/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. Identify Soledad theme installation
    Check wp-content/themes/soledad/ folder for style.css and read the version from the theme header comment
    Affected if The Soledad theme is installed and the version is 8.5.9 or lower
  2. Confirm theme version number
    Locate the 'Version:' field in the theme's style.css file header
    Affected if The installed version is 8.5.9 or any version below 8.5.10
  3. Verify AJAX endpoints are accessible
    Check if the theme registers AJAX actions for penci_archive_more_post_ajax, penci_more_post_ajax, or penci_more_featured_post_ajax in theme files (typically in functions.php or included ajax handler files)
    Affected if Any of these three AJAX action handlers are registered and accessible without authentication
  4. Test for Windows server environment
    Determine the server OS type (the LFI exploitation is specifically noted for Windows servers)
    Affected if The web server is running Windows, making the LFI path traversal exploitable for arbitrary code execution
  5. Inspect AJAX handler implementations
    Review the AJAX callback functions in the theme's PHP files to identify if include/require statements use unsanitized user input (typically a parameter like 'post_type' or similar)
    Affected if The AJAX handlers contain include/require statements using raw user-supplied parameters without proper sanitization or validation

You are affected if the Soledad theme version is 8.5.9 or lower, the vulnerable AJAX endpoints are active, and the server is running Windows, allowing unauthenticated path traversal to execute arbitrary PHP code.

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 the Soledad theme to the latest version (8.5.10 or later) which should contain the patch for this LFI vulnerability. If immediate updating is not possible, consider disabling the affected AJAX endpoints via web server configuration or .htaccess rules to block path traversal attempts.

Recommended fix Moderate confidence

Soledad theme version 8.6.0 or later

  1. 1. Check the current version of the Soledad theme installed on your WordPress site
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. 3. If a newer version of the Soledad theme is available, click Update Now
  4. 4. After updating, verify the new version number in the Themes section
  5. 5. Test critical site functionality to ensure the update did not break existing features
  6. 6. If automatic updates are not enabled, consider enabling them or regularly checking for theme updates
Caveat Review theme settings and customizations after upgrade as minor styling changes may occur

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.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-2024-11289 — 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-11289 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