CVE-2024-52497
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 quomodosoft Shopready shopready-elementor-addon allows PHP Local File Inclusion.This issue affects Shopready: from n/a through <= 3.6.
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 confidenceA Local File Inclusion (LFI) vulnerability in the Shopready Elementor addon allows attackers to include arbitrary PHP files from the server by manipulating file path parameters in include/require statements. This stems from insufficient validation of user-supplied input used in PHP file inclusion functions.
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 Shopready Elementor addon installationLocate the Shopready plugin in your WordPress installation under wp-content/plugins/ and check the main plugin file (usually shopready.php or similar) for the version number defined in the plugin header comment.Affected if The plugin is installed and the version is unknown or within any unpatched range.
-
Identify vulnerable file inclusion endpointsSearch the plugin directory for PHP files containing include(), require(), include_once(), or require_once() statements that use variables in the file path. Look for patterns like 'include($var)' or 'require($_GET[...])' without proper validation.Affected if Files using dynamic file inclusion with variables that could be user-controlled exist in the plugin.
-
Check for unsanitized user input in inclusion functionsExamine the identified inclusion code to determine if the variable passed to include/require comes directly from $_GET, $_POST, or $_REQUEST parameters without validation through functions like basename(), realpath(), or whitelist checks.Affected if User-supplied input from request parameters flows directly to file inclusion functions without sanitization.
-
Verify directory traversal protection is absentReview the code around file inclusion functions for the absence of basename() calls, path traversal removal, or whitelist validation. Check if sequences like '../' can be used to traverse directories.Affected if The code does not strip directory traversal sequences and allows arbitrary file path manipulation.
You are affected if the Shopready Elementor addon is installed and contains code that uses user input directly in PHP include/require statements without validation or path sanitization.
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 dataImplement strict whitelist-based input validation for file path parameters, use basename() to strip directory traversal sequences, and avoid using user input directly in include/require statements. Consider upgrading to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52497 — 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-52497 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