CVE-2025-8470
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 classified as critical was found in SourceCodester Online Hotel Reservation System 1.0. This vulnerability affects unknown code of the file /admin/deleteroom.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
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 SourceCodester Online Hotel Reservation System 1.0's /admin/deleteroom.php file allows remote attackers to inject malicious SQL queries through the unprotected 'ID' parameter, potentially enabling data exfiltration, authentication bypass, or complete database compromise.
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.
-
Identify the installed application versionLocate the application files and check for version indicators such as a version.php file, README, or changelog in the web root directory. Alternatively, check the HTTP response headers or the application's admin panel footer for the version number.Affected if The installed version is Fabian Online Hotel Reservation System version 1.0
-
Verify the vulnerable file existsCheck if the file /admin/deleteroom.php exists in the web server's document root by attempting to access it via HTTP request (e.g., GET http://[target]/admin/deleteroom.php) or by inspecting the filesystem if you have access.Affected if The file /admin/deleteroom.php is present and accessible on the server
-
Confirm the ID parameter is acceptedSend a test request to /admin/deleteroom.php with an ID parameter (e.g., ?ID=1) and observe whether the application processes it without error or SQL validation messages in the response.Affected if The application accepts the ID parameter and processes it without parameterized query handling
-
Check admin panel accessibilityVerify that the /admin/ directory is accessible without authentication or with low-privilege credentials, as the SQL injection requires the attacker to reach the deleteroom.php endpoint.Affected if The admin panel or deleteroom.php endpoint is accessible to unauthenticated or low-privilege users
You are affected if you are running Fabian Online Hotel Reservation System version 1.0 and the /admin/deleteroom.php file is accessible with an unprotected ID parameter.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements, implement strict input validation on the ID parameter, apply principle of least privilege to database accounts, and conduct thorough code review of other admin panel files for similar injection flaws.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8470 — 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-8470 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