CVE-2026-7698
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 identified in Tiandy Easy7 Integrated Management Platform 7.17.0. Affected by this vulnerability is an unknown functionality of the file /Easy7/rest/systemInfo/updateDbBackupInfo. Such manipulation of the argument week leads to os command injection. The attack can be executed remotely. The exploit is publicly available and might 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 confidenceOS command injection vulnerability in Tiandy Easy7 Integrated Management Platform 7.17.0. The /Easy7/rest/systemInfo/updateDbBackupInfo endpoint accepts user input through the 'week' parameter that is unsafely passed to system shell commands, allowing remote attackers to execute arbitrary OS commands.
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 installationLocate the Tiandy Easy7 Integrated Management Platform in your environment - this is typically a web-based management system. Check your inventory of deployed software or scan for the Easy7 web interface.Affected if Tiandy Easy7 Integrated Management Platform is not present in your environment
-
Determine installed versionAccess the Easy7 web interface or check system files for the version number. The affected version is 7.17.0.Affected if The installed version is 7.17.0
-
Verify vulnerable endpoint existsCheck if the URL path /Easy7/rest/systemInfo/updateDbBackupInfo is accessible on your Easy7 server. This is typically on port 8080 or 80.Affected if The endpoint /Easy7/rest/systemInfo/updateDbBackupInfo is reachable from your network
-
Confirm week parameter is acceptedSend a benign HTTP POST request to the /Easy7/rest/systemInfo/updateDbBackupInfo endpoint including a 'week' parameter with a test value (e.g., week=1). Check if the application accepts and processes this parameter.Affected if The 'week' parameter is accepted and processed by the endpoint without proper validation
You are affected if Tiandy Easy7 version 7.17.0 is running and the /Easy7/rest/systemInfo/updateDbBackupInfo endpoint with the 'week' parameter is accessible in your environment.
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 input validation/sanitization to the week parameter, refactor to use parameterized commands instead of shell string concatenation, or implement network segmentation/WAF rules to block exploitation until vendor patch is available.
- 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-7698 — 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-7698 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