CVE-2024-56230
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Maidul Dynamic Product Category Grid, Slider for WooCommerce dynamic-product-categories-design allows PHP Local File Inclusion.This issue affects Dynamic Product Category Grid, Slider for WooCommerce: from n/a through <= 1.1.3.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Dynamic Product Category Grid, Slider for WooCommerce WordPress plugin (versions up to 1.1.3). The plugin fails to properly validate or sanitize input used in include/require statements, allowing attackers to craft HTTP requests that include arbitrary local PHP files. This can lead to remote code execution if the attacker can control the included file path or if sensitive files are exposed.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the plugin is installedLocate the plugin directory in your WordPress installation under wp-content/plugins/ and identify if a folder related to 'dynamic-product-category-grid' or 'woo-product-category' exists.Affected if The plugin directory is present in the WordPress plugins folder.
-
Determine the installed plugin versionOpen the plugin's main PHP file or readme.txt within the plugin directory and locate the 'Version:' header field. Compare this version number to the affected range (versions up to and including 1.1.3).Affected if The installed version is 1.1.3 or any earlier version.
-
Identify the inclusion vulnerability entry pointReview the plugin's PHP source files, focusing on any use of include, require, include_once, or require_once statements that incorporate request parameters (such as $_GET, $_POST, or $_REQUEST) without proper sanitization.Affected if The plugin code contains include/require statements that directly use unsanitized user input.
-
Check for directory traversal patterns in HTTP trafficReview web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for incoming requests containing '../' patterns or direct file path references in query parameters that may indicate LFI exploitation attempts.Affected if Suspicious requests with '../' traversal or file inclusion patterns are found in logs targeting this plugin.
-
Inspect for recently modified or unexpected PHP filesExamine the wp-content/uploads/ directory and other writable locations for newly created or modified PHP files that may indicate successful exploitation and code execution.Affected if Unexpected PHP files appear in writable directories, suggesting possible exploitation.
You are affected if the Dynamic Product Category Grid, Slider for WooCommerce plugin is installed and its version is 1.1.3 or earlier, and the plugin contains vulnerable include/require logic using unsanitized input.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest patched version once released. Until then, disable the plugin or implement WAF rules to block directory traversal patterns (../) and suspicious file inclusion parameters in HTTP requests.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56230 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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