CVE-2025-9002
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 identified in Surbowl dormitory-management-php 1.0. This affects an unknown part of the file login.php. The manipulation of the argument Account leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.
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 · high confidenceSQL injection vulnerability in Surbowl dormitory-management-php 1.0 login.php. The 'Account' parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. This critical flaw (CVSS 9.8) enables potential authentication bypass and unauthorized database access.
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.
-
Locate the login.php fileSearch your web server document root for the login.php file that is part of the Surbowl Dormitory Management Php application. Common paths include /var/www/html/, /www/, or your web root directory. Use: find / -name 'login.php' 2>/dev/null | xargs grep -l 'dormitory' 2>/dev/nullAffected if The file exists and belongs to Surbowl Dormitory Management Php version 1.0
-
Verify the application versionCheck for version indicators in the application. Look for a version.php file, README file, or any file containing '1.0' or version information within the application directory.Affected if The installed version is Surbowl Dormitory Management Php 1.0
-
Inspect the Account parameter handling in login.phpExamine login.php for how the 'Account' parameter is processed. Look for SQL queries that directly include the Account parameter without using prepared statements or parameter binding. Search for patterns like: $_POST['Account'] or $_GET['Account'] used in SQL strings.Affected if The Account parameter is used directly in SQL queries without sanitization or prepared statements
-
Confirm network accessibilityDetermine if the login.php page is accessible from the network. Check your web server configuration and firewall rules to see if the application is exposed to external connections.Affected if The vulnerable login.php is reachable from the network (especially the internet)
You are affected if the Surbowl Dormitory Management Php 1.0 application is installed with its login.php file accessible on the network and the Account parameter is used in SQL queries without parameterized preparation.
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.
dbcve · scopedSince the product is end-of-life and unsupported, immediate mitigation requires restricting network access, deploying a WAF in front of the application, or migrating to a supported dormitory management solution. If continuing with this codebase, refactor login.php to use parameterized queries/prepared statements for all database interactions.
- 1. Stop using Dormitory Management Php 1.0 immediately as it is no longer supported by the maintainer and contains a critical SQL injection vulnerability (CVSS 9.8).
- 2. Assess your current deployment and identify all systems using this software.
- 3. Migrate to an actively maintained alternative dormitory management solution that receives security updates.
- 4. If migration is not immediately possible, implement the following compensating controls: disable the application from external network access by restricting it to localhost or an internal VPN, implement web application firewall (WAF) rules to detect and block SQL injection attempts, and monitor network traffic for indicators of compromise.
- 5. Review access logs for any signs of exploitation attempts targeting the login.php endpoint.
- 6. Plan and execute a complete migration to supported software as a priority.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9002 — 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-2025-9002 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