CVE-2026-10253
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 detected in itsourcecode Online House Rental System 1.0. This impacts an unknown function of the file /manage_payment.php. The manipulation of the argument ID results in sql injection. It is possible to launch the attack remotely. The exploit is now 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 · moderate confidenceSQL injection vulnerability in itsourcecode Online House Rental System 1.0's manage_payment.php file. The ID parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. A public exploit exists, making immediate remediation critical.
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.
-
Confirm the application is installedLocate the itsourcecode Online House Rental System installation by searching for manage_payment.php or checking web server document roots for PHP files containing 'Online House Rental' or similar brandingAffected if The application is itsourcecode Online House Rental System version 1.0
-
Verify manage_payment.php existsSearch the web server filesystem for the file /manage_payment.php or manage_payment.php within the application's web directoryAffected if The file manage_payment.php exists in the application
-
Check if ID parameter is used unsafelyOpen manage_payment.php and search for usage of $_GET['ID'] or $_POST['ID'] directly in SQL query strings without proper escaping, prepared statements, or parameter bindingAffected if The ID parameter is used directly in SQL queries without sanitization or prepared statements
-
Determine if the page is accessibleAccess the manage_payment.php file via HTTP/HTTPS request (e.g., GET /manage_payment.php?ID=test or similar) to confirm the endpoint is reachableAffected if The manage_payment.php endpoint is accessible over the network without authentication or with minimal authentication
If the itsourcecode Online House Rental System 1.0 is installed with a reachable manage_payment.php file that uses the ID parameter directly in unsanitized SQL queries, the environment is affected by CVE-2026-10253.
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 in manage_payment.php, perform input validation on all user-supplied parameters, and conduct a broader code review to identify similar injection points across the application.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10253 — 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-10253 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