CVE-2026-9465
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 Tiandy Easy7 Integrated Management Platform 7.17.0. This vulnerability affects unknown code of the file /Easy7/apps/WebService/GetDBDataEx.jsp. Performing a manipulation of the argument strTBName results in sql injection. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 Tiandy Easy7 Integrated Management Platform v7.17.0 allows remote attackers to execute arbitrary SQL commands via the strTBName parameter in the GetDBDataEx.jsp file located at /Easy7/apps/WebService/. The vulnerability is remotely exploitable and public exploits are 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.
-
Identify Tiandy Easy7 IMS installationSearch for Tiandy Easy7 IMS in installed programs (Windows) or check for /opt or /usr/local directories containing 'tiandy' or 'easy7' (Linux). Look for the IMS service running on common ports like 8080, 8443, or 80.Affected if Tiandy Easy7 IMS software is found on the system
-
Check installed IMS versionLocate the version information in the IMS installation directory, typically in a version file, about page, or the main application executable. Compare the version number to 7.17.0.Affected if The installed version is exactly 7.17.0 or falls within the affected range around 7.17.0
-
Locate GetDBDataEx.jsp fileCheck the web application root directory for the presence of GetDBDataEx.jsp. This file is typically in the webapps or htdocs directory of the IMS installation.Affected if The GetDBDataEx.jsp file exists in the web application directory
-
Verify strTBName parameter accessibilityExamine web server access logs for requests to GetDBDataEx.jsp with the strTBName parameter. Also check if the endpoint responds to valid requests.Affected if The GetDBDataEx.jsp endpoint is accessible and accepts the strTBName parameter
-
Review logs for SQL injection attemptsSearch web server access and error logs for patterns like 'GetDBDataEx.jsp?strTBName=' combined with SQL keywords (UNION, SELECT, INSERT, '--', etc.).Affected if Malicious SQL injection payloads targeting strTBName appear in logs, confirming active exploitation attempts
The environment is affected if Tiandy Easy7 IMS version 7.17.0 is installed and the GetDBDataEx.jsp endpoint with the strTBName parameter is accessible.
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 dataApply vendor patch if available. Otherwise, implement strict input validation with parameterized queries on the affected endpoint, deploy a web application firewall as a compensating control, and restrict network access to the vulnerable service.
- 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-9465 — 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-9465 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