dbcve.org
House Rental Management SystemApplication · Codeastro

CVE-2024-2076

HIGH · 7.5 CVSS v3.1 Published 2024-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in CodeAstro House Rental Management System 1.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the file booking.php/owner.php/tenant.php. The manipulation leads to missing authentication. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-255392.

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 confidence

Authentication bypass vulnerability in CodeAstro House Rental Management System 1.0 affecting booking.php, owner.php, and tenant.php files. The application fails to enforce proper authentication checks on certain functionalities, allowing unauthenticated remote attackers to access sensitive operations. The public disclosure of this vulnerability increases exploitation risk.

MitigationImplement proper authentication enforcement across all affected PHP files (booking.php, owner.php, tenant.php) and conduct access control verification across the entire application. Consider adding session validation and role-based access controls.

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
House Rental Management SystemApplication
Affected:= 1.0

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CodeAstro House Rental Management System is installed
    Locate the application web directory and look for PHP files associated with the house rental system. Check for presence of the typical application structure including the three affected files: booking.php, owner.php, and tenant.php.
    Affected if The application files exist in the web directory and any of the three vulnerable PHP files (booking.php, owner.php, tenant.php) are present.
  2. Confirm the installed version is 1.0
    Check the application for a version identifier. Look in README files, configuration files, or the main index.php for a version string. Compare against the affected version range.
    Affected if The installed version is exactly 1.0.
  3. Verify authentication enforcement on affected endpoints
    Attempt to access booking.php, owner.php, and tenant.php directly via HTTP request without providing valid credentials. Check if the files return sensitive content or functional pages without requiring login.
    Affected if The affected files are accessible and return functional content or sensitive data without any authentication token, session, or login redirect.
  4. Inspect source code for authentication logic gaps
    Open booking.php, owner.php, and tenant.php in a text editor. Search for session validation functions, authentication checks, or include statements that verify user identity before allowing access to functionality.
    Affected if The PHP files lack proper session validation checks at the beginning of the script or do not redirect unauthenticated users to a login page.

A user is affected if CodeAstro House Rental Management System version 1.0 is installed with the vulnerable PHP files (booking.php, owner.php, tenant.php) accessible and lacking proper authentication enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication enforcement across all affected PHP files (booking.php, owner.php, tenant.php) and conduct access control verification across the entire application. Consider adding session validation and role-based access controls.

Fix this in House Rental Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2076 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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