CVE-2026-10252
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 security vulnerability has been detected in itsourcecode Online House Rental System 1.0. This affects an unknown function of the file /manage_tenant.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly 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 itsourcecode Online House Rental System 1.0's /manage_tenant.php file where the ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Verify the itsourcecode Online House Rental System is installedLocate the web application's installation directory. Check for the presence of manage_tenant.php file in the web root or application directory.Affected if The application directory contains manage_tenant.php from the itsourcecode Online House Rental System version 1.0
-
Confirm the application versionInspect manage_tenant.php for version strings, check any version file or footer in the application, or compare the file creation/modification date to known release timelines.Affected if The installed version is 1.0 or an unpatched version of the Online House Rental System
-
Identify if the ID parameter is exposedReview manage_tenant.php to locate the code handling the ID parameter in GET or POST requests. Check if the parameter is used in SQL queries without prepared statements.Affected if The ID parameter from manage_tenant.php is processed through dynamic SQL queries without parameterized binding
-
Test for SQL injection vulnerabilityUsing a safe, authorized test environment, send a crafted ID parameter value such as ID=1' OR '1'='1 to the manage_tenant.php endpoint and observe if unexpected database data is returned or if error messages reveal database structure.Affected if The application returns database errors or unintended data when special characters are submitted in the ID parameter
-
Inspect the SQL query implementationOpen manage_tenant.php and search for SQL query construction patterns. Look for direct concatenation of the ID parameter into WHERE clauses, like 'SELECT * FROM ... WHERE id='.$_GET['id'].Affected if The code directly concatenates user input from the ID parameter into SQL statements without using prepared statements or input sanitization functions
The environment is affected if the itsourcecode Online House Rental System version 1.0 is deployed with manage_tenant.php accessible and the ID parameter processed through unparameterized SQL queries.
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 parameterized queries (prepared statements) for all database operations using the ID parameter, and add proper input validation to ensure only valid numeric or expected values are accepted.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10252 — 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-2026-10252 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