dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4287

HIGH · 7.3 CVSS v3.1 Published 2026-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A security flaw has been discovered in Tiandy Easy7 Integrated Management Platform 7.17.0. The affected element is an unknown function of the file /rest/devStatus/queryResources of the component Endpoint. Performing a manipulation of the argument areaId results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may 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 confidence

SQL injection vulnerability in Tiandy Easy7 Integrated Management Platform 7.17.0 allows remote attackers to inject malicious SQL queries through the areaId parameter in the /rest/devStatus/queryResources endpoint. The vulnerability affects the Endpoint component and can be exploited without authentication.

MitigationImplement WAF rules to detect and block SQL injection patterns in the areaId parameter; apply network segmentation to restrict access to the affected endpoint; implement input validation at the application layer if a vendor patch is unavailable.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tiandy Easy7 platform version
    Access the platform's web interface or check system configuration files for the version number. Look for 'Easy7' or 'Tiandy' in the application banner or version information page.
    Affected if The installed version is exactly 7.17.0, as this is the specific affected version listed in the CVE.
  2. Verify Endpoint component is enabled
    Check the platform's component list or module configuration. The vulnerability specifically affects the 'Endpoint' component. Navigate to system settings or component management in the Easy7 administration console.
    Affected if The Endpoint component is listed as active or enabled in the platform configuration.
  3. Confirm /rest/devStatus/queryResources endpoint exists
    Attempt to access the URL path /rest/devStatus/queryResources on the Easy7 server. This can be done by sending a basic HTTP GET or POST request to the endpoint using a tool like curl or a browser developer console.
    Affected if The endpoint responds with any HTTP status (200, 400, 404, etc.), indicating the endpoint is exposed and available.
  4. Inspect areaId parameter handling
    Review the application's request handling logs or use a proxy tool to intercept traffic when calling /rest/devStatus/queryResources. Check if the areaId parameter accepts user-supplied input without visible sanitization or parameterized query usage in the application logs.
    Affected if The areaId parameter accepts raw input and the application does not show evidence of SQL parameter binding in its behavior or logs.

A user is affected if they are running Tiandy Easy7 version 7.17.0 with the Endpoint component enabled and the /rest/devStatus/queryResources endpoint accessible, as the SQL injection can be exploited through the areaId parameter without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WAF rules to detect and block SQL injection patterns in the areaId parameter; apply network segmentation to restrict access to the affected endpoint; implement input validation at the application layer if a vendor patch is unavailable.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4287 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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