CVE-2026-2682
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 has been found in Tsinghua Unigroup Electronic Archives System up to 3.2.210802(62532). Impacted is an unknown function of the file /mine/PublicReport/prinReport.html?token=java. Such manipulation of the argument comid leads to sql injection. The attack can be launched 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 confidenceSQL injection vulnerability in Tsinghua Unigroup Electronic Archives System (versions up to 3.2.210802) allows remote attackers to inject malicious SQL queries via the 'comid' parameter in the /mine/PublicReport/prinReport.html file. The vulnerability is remotely exploitable with critical severity (CVSS 9.8), potentially enabling unauthorized database access, data exfiltration, or system compromise.
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<= 3.2.210802\(62532\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Tsinghua Unigroup Electronic Archives System is installedCheck your system for the presence of the Electronic Archives System application. This may be found in your web server's webroot, application directories, or system inventory. Search for files or services related to 'Electronic Archives' or 'Unigroup'.Affected if The product is found installed on the system
-
Determine the installed version numberLocate the application version information. Check for version files in the application directory, the system configuration, or the application admin interface. Common locations include version.info, about.php, or the system settings panel.Affected if The installed version is 3.2.210802 or any version up to and including 3.2.210802(62532)
-
Locate the vulnerable file prinReport.htmlSearch the web server document root for the file at path /mine/PublicReport/prinReport.html or similar paths containing 'PublicReport' and 'prinReport'. This file handles public report printing functions.Affected if The file /mine/PublicReport/prinReport.html exists on the server and is accessible via the web server
-
Test if the comid parameter is acceptedIf the vulnerable file exists, verify it accepts the 'comid' parameter by attempting a benign request (e.g., GET /mine/PublicReport/prinReport.html?comid=test). Check if the application processes this parameter without proper SQL sanitization.Affected if The application accepts the comid parameter and appears to process SQL queries based on user input without visible sanitization or parameterized query handling
A user is affected if the Tsinghua Unigroup Electronic Archives System is installed with version 3.2.210802 or lower and the /mine/PublicReport/prinReport.html endpoint is accessible and processes the comid parameter without SQL input validation.
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 dataSince the vendor is non-responsive and the product appears unmaintained, implement parameterized queries or input validation for the comid parameter in prinReport.html; consider migrating to a supported archival system if no patch becomes available.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2682 — 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-2682 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