Security Resilience

CVE-2024-39210

Info Disclosure in Mayurik Best House Rental Management System ≤ 1.0

Published
05 July 2024
Modified
21 November 2024
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0084 57th percentile
Risk Priority 65 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-39210 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability in Mayurik Best House Rental Management System. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Best House Rental Management System version 1.0 contains an arbitrary file read vulnerability triggered through the Page parameter on index.php. The flaw permits retrieval of arbitrary PHP files and other sensitive application data, carrying a CVSS 3.1 score of 7.5 that reflects network attackability, no required credentials, and high confidentiality impact.

An unauthenticated remote attacker can supply crafted values to the Page parameter and directly access restricted file contents, exposing source code, configuration details, or other internal information without any user interaction.

Public references consist of a GitHub repository that documents the issue but contain no vendor advisories, patches, or mitigation steps. The EPSS score remains flat at 0.0767 with no material increase after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Best House Rental Management System v1.0 was discovered to contain an arbitrary file read vulnerability via the Page parameter at index.php. This vulnerability allows attackers to read arbitrary PHP files and access other sensitive information within the application.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-11743Same product: Mayurik Best House Rental Management System
CVE-2025-12226Same product: Mayurik Best House Rental Management System
CVE-2024-6066Same product: Mayurik Best House Rental Management System
CVE-2024-7812Same product: Mayurik Best House Rental Management System
CVE-2024-5093Same product: Mayurik Best House Rental Management System
CVE-2024-5366Same product: Mayurik Best House Rental Management System
CVE-2024-40473Same product: Mayurik Best House Rental Management System
CVE-2024-40475Same product: Mayurik Best House Rental Management System
CVE-2024-10349Same product: Mayurik Best House Rental Management System
CVE-2024-40576Same product: Mayurik Best House Rental Management System

Affected Assets

mayurik
best house rental management system
≤ 1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized actors from obtaining sensitive information.

Information flow enforcement structurally prevents sensitive data from reaching unauthorized recipients.

Protection of information at rest prevents unauthorized exposure of stored sensitive data.

Transmission confidentiality mechanisms stop exposure of sensitive data on the wire.

Least privilege reduces the set of actors who can reach sensitive information.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.10 only requires awareness, a topic-specific acceptable-use policy stating expected behaviours/monitoring, and procedures referencing classification and other controls; per the owner's explicit rule on labelling and similar dependency-style clauses, this does not itself prevent exposure (CWE-200) unless access/DLP/etc. act on it.

blocks

Requiring the return of all physical and electronic assets plus secure deletion of organizational data from personal devices reduces the chance that sensitive information remains accessible to departing personnel.

blocks

A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule, labeling/classification does not itself prevent exposure and requires other controls (e.g. access enforcement) to act on it.

blocks

By requiring classification labels and metadata on all information assets, the control makes it harder for sensitive data to be inadvertently exposed because downstream systems and users can recognize and enforce handling rules based on those labels.

blocks

Requiring encryption, access controls, and recipient authentication for transfers directly reduces the chance that sensitive data reaches an unauthorized observer.

blocks

Secure delivery, protected storage, and confidentiality of allocation records limit exposure of authentication material to unauthorized observers.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References