dbcve.org
Easy7 CmsApplication · Tiandy

CVE-2026-3818

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 flaw has been found in Tiandy Easy7 CMS Windows 7.17.0. Impacted is an unknown function of the file /Easy7/apps/WebService/GetDBData.jsp. This manipulation of the argument strTBName causes sql injection. The attack may be initiated remotely. The exploit has been published and may 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 confidence

SQL injection vulnerability in Tiandy Easy7 CMS Windows 7.17.0 allows remote attackers to inject malicious SQL queries via the strTBName parameter in the /Easy7/apps/WebService/GetDBData.jsp endpoint, potentially leading to full database compromise.

MitigationImplement network access controls to limit exposure of the affected system, deploy WAF rules to detect and block SQL injection payloads, and monitor for indicators of compromise while awaiting vendor response or considering alternative solutions.

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
Easy7 CmsApplication
Affected:= 7.17.0

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
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 checks

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

  1. Identify if Tiandy Easy7 CMS is installed
    Check for the presence of the Easy7 application directory on the system, typically found in C:\Program Files\Tiandy\Easy7 or C:\Easy7. Also check Windows Services for 'Tiandy Easy7' or similar service entries.
    Affected if The Tiandy Easy7 CMS application is installed on the system
  2. Verify the installed version is 7.17.0
    Locate the version information in the application directory, commonly in an about dialog, version.txt file, or in the Windows installed programs list. Compare the exact version number to 7.17.0.
    Affected if The installed version is exactly 7.17.0
  3. Confirm the vulnerable endpoint is accessible
    Attempt to access the URL http://[host]/Easy7/apps/WebService/GetDBData.jsp via HTTP request. If the endpoint responds (even with an error), it is accessible.
    Affected if The GetDBData.jsp endpoint responds to HTTP requests, indicating the application is running and the endpoint is exposed
  4. Check network exposure of the affected service
    Review firewall rules, network configuration, or perform a port scan to determine if the web service ports (typically port 80 or 443) are accessible from external networks or untrusted zones.
    Affected if The Easy7 web interface is accessible from untrusted networks or the internet
  5. Identify if the strTBName parameter is accepted
    Send a test request to the endpoint with a parameter such as /Easy7/apps/WebService/GetDBData.jsp?strTBName=test and observe if the application processes the parameter.
    Affected if The endpoint accepts and processes the strTBName parameter without proper input validation

A system is affected if Tiandy Easy7 CMS version 7.17.0 is installed and running with the GetDBData.jsp endpoint accessible over the network, as the SQL injection vulnerability in the strTBName parameter can be exploited.

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 network access controls to limit exposure of the affected system, deploy WAF rules to detect and block SQL injection payloads, and monitor for indicators of compromise while awaiting vendor response or considering alternative solutions.

Fix this in Easy7 Cms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3818 — 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-3818 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