CVE-2024-52501
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 WebbyTemplate Office Locator office-locator.This issue affects Office Locator: from n/a through <= 1.3.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 confidenceA Remote File Inclusion (RFI) vulnerability in the WebbyTemplate Office Locator PHP application allows attackers to include remote files via unsanitized user input in include/require statements. This can lead to arbitrary code execution on the server.
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.
-
Locate WebbyTemplate Office Locator installationSearch the web server document root for files or directories named 'officelocator', 'officelocator.php', or containing the application name in headers/footers. Common paths: /var/www/html/, /home/*/public_html/, or C:\inetpub\wwwroot\Affected if The application files are present on the server
-
Identify PHP version in useRun 'php -v' from command line or create a PHP file containing '<?php echo phpversion(); ?>' and access it via browserAffected if PHP version is current (older unpatched versions may have additional risks but this CVE is application-specific)
-
Check PHP allow_url_include settingRun 'php -i | grep allow_url_include' or check php.ini file for 'allow_url_include = On'Affected if allow_url_include is enabled (set to On) - this is required for remote file inclusion to succeed
-
Search for vulnerable include/require patternsGrep the application source code for 'include($_' or 'require($_' or 'include($_GET' or 'require($_POST' patterns without sanitization functions like basename() or realpath()Affected if User-supplied input (GET, POST, REQUEST) is used directly in include/require statements without validation
-
Inspect HTTP parameters for file inclusion pointsReview application code for parameters that accept file paths (e.g., '?page=', '?file=', '?path=') and trace whether these reach include/require statementsAffected if URL parameters control include/require paths without whitelist or sanitization
You are affected if the WebbyTemplate Office Locator application is installed AND PHP's allow_url_include is enabled AND user input flows unsanitized into include/require statements.
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 inclusion paths, disable allow_url_include in php.ini, and refactor code to avoid using user-supplied input in include/require statements.
- 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-52501 — 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-52501 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