CVE-2026-5823
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 weakness has been identified in itsourcecode Construction Management System 1.0. Affected by this issue is some unknown functionality of the file /borrowed_tool_report.php. This manipulation of the argument Home causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks.
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 Construction Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'Home' parameter in /borrowed_tool_report.php. The exploit is publicly available, increasing the risk of active exploitation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 itsourcecode Construction Management System is installedCheck your web server document root for the presence of the 'itsourcecode' or 'construction' system directories, or search for borrowed_tool_report.php using: find /var/www -name 'borrowed_tool_report.php' 2>/dev/null (Linux) or dir /s /b C:\borrowed_tool_report.php (Windows)Affected if The system is itsourcecode Construction Management System and borrowed_tool_report.php exists
-
Identify the installed versionCheck for version indicators in the application - look for version.php, CHANGELOG.txt, or admin/config pages that display the software versionAffected if The version is 1.0 or earlier (no patched version confirmed, so any version should be considered potentially affected)
-
Examine borrowed_tool_report.php for vulnerable SQL usageOpen borrowed_tool_report.php and search for SQL queries containing the 'Home' parameter, for example: grep -n 'Home' borrowed_tool_report.php and look for query patterns like $_GET['Home'] or $_POST['Home'] used directly in SQL statements without prepared statements or escaping functionsAffected if The 'Home' parameter is used directly in SQL queries without parameterized queries or proper sanitization (e.g., no mysqli_prepare, PDO::prepare, or escaping functions like mysqli_real_escape_string)
-
Check if the application processes borrowed tool reportsReview application logs or access records for requests to /borrowed_tool_report.php, or test by accessing the page directly if the application is runningAffected if The borrowed_tool_report.php page is accessible and the 'Home' parameter can be submitted via GET or POST requests
A user is affected if they run itsourcecode Construction Management System version 1.0 with borrowed_tool_report.php accessible and the 'Home' parameter used directly in unsanitized 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 dataReplace dynamic SQL queries with parameterized statements (prepared statements) in borrowed_tool_report.php for the 'Home' parameter, and implement proper input validation on all user-supplied parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5823 — 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-5823 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