CVE-2024-46377
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 · uneditedBest House Rental Management System 1.0 contains an arbitrary file upload vulnerability in the save_settings() function of the file rental/admin_class.php.
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 confidenceBest House Rental Management System 1.0 has an arbitrary file upload vulnerability in the save_settings() function within rental/admin_class.php. An attacker with administrative access can upload malicious files (e.g., web shells) to the server, potentially achieving remote code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Best House Rental Management System is installedLocate the application files - typically in the web server document root. Look for directories such as 'rental' or files named 'index.php', 'admin_class.php', or application-specific branding files.Affected if The application is present on the server in any web-accessible directory.
-
Confirm the installed version is 1.0Search for version indicators - check for version.php, README files, or look for version strings in source code comments or configuration files. Also check the login page or admin dashboard for version information.Affected if The installed version is exactly 1.0 (the only affected version per the CVE).
-
Locate rental/admin_class.php and inspect save_settings()Navigate to rental/admin_class.php in the application directory. Open the file and locate the save_settings() function. Examine whether it contains file upload handling logic (search for $_FILES, move_uploaded_file, or file upload references).Affected if The file rental/admin_class.php exists and the save_settings() function handles file uploads without proper validation.
-
Determine if administrative access is enabledCheck if the application admin panel is accessible - typically at /admin, /rental/admin, or similar paths. Verify that administrator accounts can be created or accessed.Affected if Administrative login is functional and accessible.
-
Identify upload directory and web accessibilityExamine the save_settings() function code to determine the upload path. Check if uploaded files are stored within the web document root (htdocs, public_html, www) and if the directory allows script execution.Affected if Uploads are stored in a web-accessible directory where uploaded files can be executed (e.g., .php files can be served).
If Best House Rental Management System version 1.0 is installed with the rental/admin_class.php file containing an unprotected save_settings() upload function, and the admin panel is accessible, the environment is vulnerable to arbitrary file upload and potential remote code execution.
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 server-side file type validation (allowlist approach), sanitize filenames, store uploads outside the webroot or in non-executable directories, and disable script execution in upload directories.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46377 — 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-46377 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