dbcve.org
Dormitory Management SystemApplication · Code Projects

CVE-2024-0472

HIGH · 7.5 CVSS v3.1 Published 2024-01-12
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 code-projects Dormitory Management System 1.0. It has been rated as problematic. This issue affects some unknown processing of the file modifyuser.php. The manipulation of the argument mname leads to information disclosure. The exploit has been disclosed to the public and may be used. The identifier VDB-250577 was assigned to this vulnerability.

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

Information disclosure vulnerability in the Dormitory Management System 1.0's modifyuser.php file. The mname parameter is not properly handled, allowing unauthorized access to sensitive data. This appears to be a classic case of improper access control or input validation on the user modification function.

MitigationImplement proper authorization checks on the modifyuser.php endpoint and validate/sanitize the mname parameter. Restrict access to user modification functions to authenticated and authorized users only. Review similar parameters in other PHP files for similar issues.

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
Dormitory 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 Dormitory Management System is installed
    Locate PHP application files and verify the presence of a dormitory management system, typically found in web server document roots. Check for files like modifyuser.php, login.php, or database configuration files that indicate this specific application.
    Affected if The Code Projects Dormitory Management System version 1.0 is present on the server
  2. Verify the application version
    Check for version indicators such as version.php files, README files, or footer/branding elements that display the software version. Compare the installed version to the affected range (version 1.0).
    Affected if The installed version is exactly 1.0 (the only affected version)
  3. Confirm modifyuser.php file exists
    Search the web application directory structure for the modifyuser.php file in user-accessible paths, typically under admin, user, or root directories of the application.
    Affected if The modifyuser.php file exists in the application
  4. Check authentication status on modifyuser.php
    Inspect the modifyuser.php source code to determine if it includes authentication checks (such as session verification, login validation, or role-based access control) at the beginning of the file before processing the mname parameter.
    Affected if The file lacks proper authentication/authorization checks before processing user input
  5. Inspect mname parameter handling
    Examine the modifyuser.php source code to see how the mname parameter is processed. Look for whether the parameter is used directly in queries without sanitization, or whether it exposes sensitive user data without access controls.
    Affected if The mname parameter is processed without proper input validation or exposes sensitive data without access restrictions

The environment is affected if the Code Projects Dormitory Management System version 1.0 is installed and the modifyuser.php file processes the mname parameter without proper authentication and input validation.

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 authorization checks on the modifyuser.php endpoint and validate/sanitize the mname parameter. Restrict access to user modification functions to authenticated and authorized users only. Review similar parameters in other PHP files for similar issues.

Fix this in Dormitory Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0472 — 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-0472 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