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

CVE-2024-10871

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-09
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
The Category Ajax Filter plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.8.2 via the 'params[caf-post-layout]' parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary 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 files with a .php extension can be uploaded and included.

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 Category Ajax Filter WordPress plugin versions up to 2.8.2 contain an unauthenticated Local File Inclusion vulnerability via the 'params[caf-post-layout]' parameter. Attackers can include arbitrary server files and execute any PHP code contained within them, enabling full remote code execution.

MitigationUpdate the Category Ajax Filter plugin to the latest version to patch the file inclusion vulnerability; if immediate update is not possible, consider disabling the plugin or implementing WAF rules to block requests to the vulnerable parameter.

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. Identify if Category Ajax Filter plugin is installed
    Check WordPress plugins directory (wp-content/plugins/) for 'category-ajax-filter' folder, or view installed plugins in wp-admin under Plugins > Installed Plugins
    Affected if The Category Ajax Filter plugin is present in the WordPress installation
  2. Determine installed plugin version
    Open the main plugin file (usually category-ajax-filter.php) and locate the version comment or header, or check the plugin details in WordPress admin plugins list
    Affected if Version is 2.8.2 or any version up to 2.8.2 (no fixed version indicated)
  3. Confirm plugin is active
    Check WordPress admin under Plugins > Installed Plugins to verify the plugin status is 'Active'
    Affected if Plugin is activated and handling requests
  4. Verify AJAX endpoint is publicly accessible
    Test access to the plugin's AJAX PHP file (typically /wp-admin/admin-ajax.php with 'action' parameter related to the plugin) without authentication
    Affected if The AJAX endpoint responds without requiring login, allowing unauthenticated parameter submission
  5. Inspect server access logs for exploitation attempts
    Review web server access logs (Apache/Nginx) for requests containing 'params[caf-post-layout]' parameter patterns that may indicate LFI probing
    Affected if Suspicious requests with the vulnerable parameter are found in logs, suggesting attempted or successful exploitation

A WordPress site is affected if the Category Ajax Filter plugin is installed with version 2.8.2 or below and the plugin is active, allowing unauthenticated users to submit the vulnerable 'params[caf-post-layout]' parameter.

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 Category Ajax Filter plugin to the latest version to patch the file inclusion vulnerability; if immediate update is not possible, consider disabling the plugin or implementing WAF rules to block requests to the vulnerable parameter.

Recommended fix High confidence

Version 2.8.3 or later of the Category Ajax Filter plugin

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Category Ajax Filter' plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, manually download the latest version from wordpress.org/plugins/category-ajax-filter/ and upload via Plugins > Add New > Upload Plugin
  6. Verify the updated version is 2.8.3 or higher in the Plugins list
Caveat Minimal risk - this is a security patch update for a bugfix release; always backup before updating

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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