dbcve.org
E Document SystemApplication · Eic

CVE-2021-22860

CRITICAL · 9.8 CVSS v3.1 Published 2021-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 →
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
EIC e-document system does not perform completed identity verification for sorting and filtering personnel data. The vulnerability allows remote attacker to obtain users’ credential information without logging in the system, and further acquire the privileged permissions and execute arbitrary commends.

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 · moderate confidence

The EIC e-document system contains an authentication bypass vulnerability in its personnel data sorting and filtering functionality. The system fails to properly verify user identity when processing requests for personnel data, allowing unauthenticated attackers to retrieve user credentials. Successful exploitation enables attackers to escalate privileges and execute arbitrary commands on the system.

MitigationImplement comprehensive authentication and authorization checks on all personnel data endpoints, enforce proper session validation, and apply the principle of least privilege to prevent unauthorized access to credential information.

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
E Document SystemApplication
Affected:= 2.9= 3.0.2

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 installed version of EIC e-document system
    Locate the system version information in the application metadata, about page, or system configuration files. Common locations include: version.txt, system info panel, or the application's main DLL/version resource.
    Affected if The installed version is 2.9 or 3.0.2 specifically.
  2. Verify personnel data module is exposed
    Check if the personnel data sorting and filtering functionality is accessible in the running application. This typically involves identifying endpoints related to personnel, user data, or employee records in the application's URL structure or API routes.
    Affected if The personnel data sorting/filtering feature is enabled and reachable via HTTP/HTTPS requests.
  3. Test unauthenticated access to personnel endpoints
    Send an HTTP request to personnel-related endpoints without providing authentication credentials or session tokens. Common endpoint patterns include paths containing terms like 'personnel', 'users', 'employee', 'sort', or 'filter' with the application's base URL.
    Affected if The system returns personnel data, user credentials, or sensitive employee information without requiring authentication.
  4. Inspect access control configuration
    Review the application's configuration files, web.xml, or security policy settings to determine if authentication is enforced on personnel data endpoints. Look for any misconfigured or disabled access control rules.
    Affected if Authentication and authorization checks are missing, disabled, or improperly configured for personnel data endpoints.

A user is affected if the EIC e-document system version is 2.9 or 3.0.2 AND the personnel data sorting/filtering functionality is exposed and accessible without authentication, allowing credential retrieval.

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 comprehensive authentication and authorization checks on all personnel data endpoints, enforce proper session validation, and apply the principle of least privilege to prevent unauthorized access to credential information.

Fix this in E Document System Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
48.0 hours of engineering $8,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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