CVE-2026-5620
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 has been found in itsourcecode Construction Management System 1.0. Affected is an unknown function of the file /borrowed_equip_report.php of the component Parameter Handler. The manipulation of the argument Home leads to sql injection. It is possible to initiate the attack 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 · moderate confidenceSQL injection vulnerability in itsourcecode Construction Management System 1.0 at the /borrowed_equip_report.php file. The 'Home' parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries through the Parameter Handler component.
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.
-
Locate the vulnerable PHP fileSearch the web server document root for the file borrowed_equip_report.php. Common paths include /var/www/html/, /www/, or the application's root directory. Use: find /var/www -name "borrowed_equip_report.php" 2>/dev/nullAffected if The file borrowed_equip_report.php exists in the application directory
-
Verify the application is itsourcecode Construction Management SystemCheck the application for version information. Look in README files, footer of web pages, or admin panels for version 1.0. Also verify the application name matches 'itsourcecode Construction Management System'Affected if The installed application is itsourcecode Construction Management System version 1.0
-
Confirm the vulnerable parameter existsExamine borrowed_equip_report.php and locate the 'Home' parameter handling code. The vulnerable code will contain direct use of $_GET['Home'] or $_POST['Home'] in a SQL query without sanitizationAffected if The file contains unsanitized 'Home' parameter used in database queries
-
Test if the Parameter Handler component is activeCheck if borrowed_equip_report.php is accessible via web request and receives the 'Home' parameter. Attempt a basic request: curl "http://TARGET/borrowed_equip_report.php?Home=test"Affected if The page accepts the 'Home' parameter and returns a response without error blocking the input
-
Check for web application firewall or input filteringReview any WAF configurations, web server filters, or application-level input validation that may be present between the user and borrowed_equip_report.phpAffected if No WAF or input filtering is deployed that would block malicious SQL injection attempts in the Home parameter
A user is affected if they have itsourcecode Construction Management System 1.0 installed with the borrowed_equip_report.php file accessible and the 'Home' parameter accepting unsanitized user input for database 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 queries/prepared statements for the 'Home' parameter in borrowed_equip_report.php. If a vendor patch becomes available, apply it immediately.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5620 — 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-5620 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