CVE-2025-12226
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 found in SourceCodester Best House Rental Management System 1.0. Impacted is the function save_house of the file /admin_class.php. Performing manipulation of the argument house_no results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could 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 confidenceA SQL injection vulnerability exists in the save_house function of admin_class.php in SourceCodester Best House Rental Management System 1.0. The house_no parameter is not properly sanitized, allowing attackers to inject malicious SQL queries. This critical vulnerability (CVSS 9.8) is remotely exploitable and a public exploit exists.
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 installed product versionLocate and inspect the application files for version indicators such as version.php, readme.txt, or meta headers that indicate 'Best House Rental Management System' version 1.0Affected if The installed version is SourceCodester Best House Rental Management System 1.0
-
Locate vulnerable fileSearch for the file admin_class.php in the application directory structure, typically found in the admin or class folderAffected if The file admin_class.php exists in the application
-
Verify vulnerable function existsOpen admin_class.php and search for the save_house function definition, then confirm it accepts and processes a house_no parameterAffected if The save_house function exists and handles the house_no parameter without proper sanitization
-
Check for SQL injection sinkWithin the save_house function, locate where house_no is used in SQL queries - inspect whether it is concatenated directly into the query string or passed as a raw parameterAffected if The house_no parameter is inserted directly into SQL queries without prepared statements, parameter binding, or escaping functions
-
Determine exposureCheck if the application is network-accessible and whether the save_house function is reachable via HTTP requests (typically through admin panel endpoints)Affected if The application is remotely accessible and the save_house function can be invoked with user-supplied house_no input
A user is affected if they run Best House Rental Management System 1.0 with the admin_class.php file containing a save_house function that uses the house_no parameter directly in SQL queries without prepared statements.
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 dataImplement prepared statements/parameterized queries for the house_no parameter and all user inputs in the save_house function. Additionally, apply input validation and output encoding to prevent SQL injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-12226 — 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-12226 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