CVE-2026-4288
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 weakness has been identified in Tiandy Easy7 Integrated Management Platform 7.17.0. The impacted element is an unknown function of the file /rest/devStatus/getDevDetailedInfo of the component Endpoint. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. 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 7.17.0 allows remote attackers to inject arbitrary SQL commands via the ID parameter in the /rest/devStatus/getDevDetailedInfo endpoint. The vulnerability is exploitable without authentication 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 platformAccess the web interface or check system information to confirm the installed product is Tiandy Easy7 Integrated Management PlatformAffected if The system is not running Tiandy Easy7 IMP
-
Verify version 7.17.0Check the installed software version in the platform's about or system info page, or via API enumeration, and confirm it matches exactly 7.17.0Affected if The version is not 7.17.0 (only this specific version is listed as affected)
-
Confirm endpoint accessibilitySend a GET request to /rest/devStatus/getDevDetailedInfo and verify the endpoint responds (even with an error)Affected if The endpoint does not exist or is not reachable
-
Check if ID parameter is acceptedSend a request to /rest/devStatus/getDevDetailedInfo with an ID parameter (e.g., ID=1) and observe the response behaviorAffected if The ID parameter is not processed or accepted by the endpoint
-
Verify no authentication is requiredAttempt the request without any session cookie, Authorization header, or authentication tokenAffected if Authentication is required to access the endpoint (the vulnerability requires unauthenticated access)
You are affected if the system is Tiandy Easy7 IMP version 7.17.0 and the /rest/devStatus/getDevDetailedInfo endpoint accepts an ID parameter without requiring authentication.
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 dataImplement parameterized queries/prepared statements for the ID parameter, apply input validation, or deploy a WAF rule to block SQL injection payloads until vendor patch is available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4288 — 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-4288 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