CVE-2024-12357
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 · uneditedA vulnerability was found in SourceCodester Best House Rental Management System 1.0 and classified as problematic. Affected by this issue is some unknown functionality of the file /index.php. The manipulation of the argument page leads to file inclusion. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceThe Best House Rental Management System 1.0 contains a file inclusion vulnerability in /index.php where the 'page' parameter is not properly validated, allowing attackers to include arbitrary local or potentially remote files. This can lead to sensitive information disclosure (reading system files like /etc/passwd) or remote code execution if remote file inclusion is enabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Verify Best House Rental Management System is installedLocate the application by searching for the /index.php file in the web root directory, or check if the application's login page or main interface is accessible via HTTP/HTTPSAffected if The application files exist in the web directory and the service is running
-
Confirm the installed version is 1.0Check the application version by reviewing any version file, footer text on pages, or admin panel information. Compare against the affected version range (1.0)Affected if The application version is exactly 1.0
-
Check if the vulnerable /index.php endpoint accepts the page parameterAccess the URL pattern /index.php?page= (without a value) and observe if the application processes the parameter or returns an error related to the page parameterAffected if The application accepts and processes the 'page' parameter without proper validation
-
Test for local file inclusion vulnerabilityAttempt to include a known local file by requesting /index.php?page=../../../../etc/passwd or similar path traversal sequences, checking if the file contents are returned in the responseAffected if The application returns contents of files outside the intended directory (such as /etc/passwd)
-
Check PHP configuration for remote file inclusion capabilityInspect the PHP configuration file (php.ini) for the allow_url_include setting, or check via phpinfo() to see if this directive is enabledAffected if allow_url_include is set to On (allows remote file inclusion)
The environment is affected if the Best House Rental Management System version 1.0 is running, the /index.php endpoint accepts an unvalidated 'page' parameter, and the application can be induced to include arbitrary local files.
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 the page parameter using a whitelist approach, disable allow_url_include in PHP, and use basename() or realpath() functions to ensure only permitted files can be included.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12357 — 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-12357 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