Command InjectionWeakness · CWE-77

CVE-2026-4585

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-23
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 vulnerability has been found in Tiandy Easy7 Integrated Management Platform up to 7.17.0. This vulnerability affects unknown code of the file /Easy7/apps/WebService/ImportSystemConfiguration.jsp of the component Configuration Handler. The manipulation of the argument File leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public 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

OS command injection vulnerability in Tiandy Easy7 Integrated Management Platform's ImportSystemConfiguration.jsp. The 'File' parameter passed to this configuration import handler is not properly sanitized before being used in OS command execution, allowing remote attackers to execute arbitrary system commands on the underlying server.

MitigationSince the vendor has not responded to the disclosure, organizations should immediately restrict network access to affected systems, implement WAF rules to block malicious input patterns in the File parameter, and consider disabling the ImportSystemConfiguration.jsp functionality if not required until an official patch is 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
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 platform is deployed
    Check for the Easy7 web interface by accessing the application's login page on common ports (typically 80, 443, 8080, 8443). Look for 'Tiandy Easy7' or 'Easy7' branding in the login page or page title.
    Affected if The system is running Tiandy Easy7 Integrated Management Platform web interface.
  2. Locate the vulnerable JSP endpoint
    Verify that the file ImportSystemConfiguration.jsp exists on the web server by attempting to access it directly: /platform/system/ImportSystemConfiguration.jsp or /easy7/platform/system/ImportSystemConfiguration.jsp (paths may vary based on installation).
    Affected if The ImportSystemConfiguration.jsp file is present and accessible via HTTP/HTTPS.
  3. Confirm the File parameter is accepted
    Send a test request to the JSP endpoint with a benign File parameter (such as File=test) and verify the application processes it without returning a 404 or authentication redirect. Use: GET /path/to/ImportSystemConfiguration.jsp?File=test
    Affected if The application accepts input for the File parameter and processes the request (even if it returns an error about the file not found).
  4. Determine the installed version
    Check the application version by reviewing the login page footer, about page, or by inspecting JavaScript files or error messages that may reveal version information. Compare against any documented version ranges for Easy7.
    Affected if The installed version of Tiandy Easy7 falls within an unpatched version range and the above vulnerable endpoint is accessible.

A system is affected if it runs Tiandy Easy7 and the ImportSystemConfiguration.jsp endpoint is accessible, accepting the File parameter without proper sanitization.

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

Since the vendor has not responded to the disclosure, organizations should immediately restrict network access to affected systems, implement WAF rules to block malicious input patterns in the File parameter, and consider disabling the ImportSystemConfiguration.jsp functionality if not required until an official patch is available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4585 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