CVE-2025-40665
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 · uneditedTime-based blind SQL injection vulnerabilities in TCMAN's GIM v11. These allow an attacker to retrieve, create, update and delete databases through ArbolID parameter in /GIMWeb/PC/frmCorrectivosList.aspx.
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 confidenceTime-based blind SQL injection in TCMAN GIM v11's /GIMWeb/PC/frmCorrectivosList.aspx page allows remote attackers to execute arbitrary SQL commands via the ArbolID parameter. The vulnerability enables complete database manipulation (read, write, update, delete) through time-based inference techniques.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 11.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify TCMAN GIM versionCheck the installed TCMAN GIM version by reviewing application binaries, installation directories, or consulting system inventory/CMDB records for the exact version numberAffected if The installed version is exactly 11.0 (version 11.0 is specifically listed as affected)
-
Locate the vulnerable web endpointVerify the existence of /GIMWeb/PC/frmCorrectivosList.aspx in the web application's directory structure or through web path enumerationAffected if The endpoint /GIMWeb/PC/frmCorrectivosList.aspx is present and accessible
-
Identify if ArbolID parameter is in useReview application logs, proxy traffic, or access logs for requests containing the ArbolID parameter being sent to frmCorrectivosList.aspxAffected if The ArbolID parameter is actively used in requests to the vulnerable endpoint
-
Test for time-based SQL injection responseSend a crafted request to /GIMWeb/PC/frmCorrectivosList.aspx with ArbolID parameter containing SQL injection payloads that induce time delays (e.g., '; WAITFOR DELAY '0:0:5'--) and measure response timeAffected if Responses exhibit delay corresponding to injected time-based queries, indicating successful blind SQL injection
A system is affected if TCMAN GIM version 11.0 is installed, the web interface is accessible, and the ArbolID parameter on frmCorrectivosList.aspx exhibits time delays in response to injected 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 queries/prepared statements for the ArbolID parameter and implement input validation. Deploy a WAF rule as an interim protective measure while remediating the code.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40665 — 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-2025-40665 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