CVE-2026-7074
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. This vulnerability affects unknown code of the file /execute1.php. Such manipulation of the argument code leads to sql injection. The attack may be performed from remote. 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 allows remote attackers to inject malicious SQL queries via the 'code' parameter in the /execute1.php file. The vulnerability is exploitable without authentication and the exploit is publicly available.
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 itsourcecode Construction Management System is installedSearch for the application in your web root directory (e.g., look for directories containing 'construction' or 'itsourcecode'), or check your installed web applications listAffected if The application is present on the server
-
Verify the vulnerable execute1.php file existsLocate the execute1.php file in the web directory structure - typically found in the application root or admin directoriesAffected if The file execute1.php exists in the application path
-
Test access to the vulnerable endpointSend a test HTTP request to /execute1.php with the 'code' parameter (e.g., GET /execute1.php?code=test) and verify the application respondsAffected if The endpoint is accessible and returns a response from the application
-
Check application versionReview any version files (VERSION, about.php, or admin panel version display) within the itsourcecode application directoryAffected if The installed version is 1.0 or cannot be determined (treat as vulnerable)
-
Review web server access logs for exploitation attemptsSearch access logs for requests to execute1.php with unusual 'code' parameter values such as SQL keywords (UNION, SELECT, INSERT), quotes, or common SQL injection payloadsAffected if Suspicious SQL injection patterns are found in logs for the execute1.php endpoint
-
Check database for indicators of compromiseReview database logs or audit tables for unauthorized queries that may have been injected through the code parameter, particularly around the time of deployment or from external IPsAffected if Unexpected or unauthorized SQL queries appear in database activity logs
The environment is affected if itsourcecode Construction Management System 1.0 is installed and the execute1.php file is accessible, since the SQL injection vulnerability requires no authentication and affects the 'code' parameter in that file.
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 execute1.php, implement strict input validation on the code parameter, and apply a web application firewall rule as a temporary control until the vendor patch is available.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7074 — 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-7074 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