CVE-2026-6007
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 itsourcecode Construction Management System 1.0. This affects an unknown function of the file /del.php. The manipulation of the argument equipname results in sql injection. The attack can be launched remotely. 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 confidenceSQL injection vulnerability in itsourcecode Construction Management System 1.0 allows remote attackers to inject malicious SQL queries via the equipname parameter in the /del.php file. The attack requires no authentication based on the medium CVSS score, and a public exploit exists, making this vulnerability immediately exploitable in the wild.
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 Construction Management System installationSearch for the itsourcecode Construction Management System by identifying the web root directory and looking for del.php. Common paths may include /del.php or /construction/del.php. Use file system search or review web server document roots.Affected if The del.php file exists in the web application directory structure.
-
Confirm the application versionReview any version files (version.txt, about.php, or configuration files) in the application root to determine if the installed version is 1.0. Check footer text or meta tags which may display version information.Affected if The installed version is 1.0 or earlier.
-
Inspect the del.php file for vulnerable codeOpen del.php and search for dynamic SQL queries that incorporate the equipname parameter without using prepared statements or parameter binding. Look for patterns like $_GET['equipname'] or $_POST['equipname'] concatenated directly into SQL strings.Affected if The equipname parameter is used in a SQL query without parameterized queries or input sanitization.
-
Test if the endpoint is accessible without authenticationAttempt to access del.php directly via HTTP/HTTPS without providing any authentication cookies or credentials. Send a request such as GET /del.php?equipname=testAffected if The del.php endpoint responds without requiring authentication and processes the equipname parameter.
If the itsourcecode Construction Management System version 1.0 is installed, the del.php file exists and handles the equipname parameter with direct SQL concatenation without prepared statements, then the environment is affected by CVE-2026-6007.
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 in del.php with parameterized queries/prepared statements, apply input validation on the equipname parameter, and consider deploying a WAF as a temporary protective measure until code fixes are implemented.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6007 — 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-6007 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