CVE-2024-54375
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Sabri Woolook woolook allows PHP Local File Inclusion.This issue affects Woolook: from n/a through <= 1.7.0.
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 confidencePath Traversal vulnerability in Sabri Woolook (versions up to 1.7.0) allows attackers to manipulate file paths in PHP include/require statements to traverse directories and include arbitrary local files, potentially leading to Remote Code Execution via Local File Inclusion (LFI).
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Identify Sabri Woolook installationLocate the Sabri Woolook installation directory and look for a version file (e.g., version.php, info.php) or check the main PHP files for a version constant or variable.Affected if The installed version is 1.7.0 or any version up to and including 1.7.0.
-
Find PHP files using include/require with dynamic pathsSearch the codebase for PHP files containing include, include_once, require, or require_once statements where the path is built from request parameters (e.g., $_GET, $_POST).Affected if Files exist that use dynamic file inclusion based on user input without proper sanitization.
-
Identify user-controlled path parametersReview the identified include/require files and trace back to determine which URL parameters control the file path (commonly named 'page', 'file', 'path', 'template', or 'view').Affected if URL parameters can be directly used in include/require statements without validation.
-
Test for path traversal capabilityIf you have access to the running application, attempt a controlled test request with '../' sequences in the identified parameter (e.g., ?page=../../etc/passwd) to verify if the application allows directory traversal.Affected if The application returns content from files outside the intended directory, confirming the vulnerability is exploitable.
-
Check PHP configuration for allow_url_includeReview the application's php.ini or check the PHP configuration via phpinfo() to see if allow_url_include is enabled.Affected if allow_url_include is On (this would allow remote file inclusion in addition to local, increasing exploit severity).
You are affected if Sabri Woolook version 1.7.0 or lower is installed AND the application uses dynamic file inclusion with user-controlled parameters that can be manipulated for path traversal.
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 input validation on all file path parameters using realpath() to canonicalize and verify the resolved path stays within an allowed directory whitelist; reject any requests containing path traversal sequences (..) or null bytes.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54375 — 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-54375 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