CVE-2026-1514VulnerabilityPublished 28 Jan 2026

CVE-2026-1514: 2100 Technology Official Document Management System · Incorrect Authorization

Affects 2100 Technology Official Document Management SystemSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
2100 TechnologyOfficial Document Management System	Affected >=5.0.77 <=5.0.98	Fixed in–

AI-suggested

European organizations should implement the following specific mitigation strategies: 1) Immediately audit and restrict user privileges to the minimum necessary, ensuring that only trusted users have access to modify front-end code or sensitive documents. 2) Deploy application-layer firewalls or web application firewalls (WAFs) with custom rules to detect and block unauthorized front-end code modification attempts. 3) Implement strict monitoring and alerting on changes to front-end code or document access patterns to quickly identify suspicious activity. 4) Enforce multi-factor authentication (MFA) to reduce the risk of credential compromise leading to exploitation. 5) Conduct regular code reviews and penetration testing focused on authorization logic within the document management system. 6) Engage with 2100 Technology for patches or updates as they become available and plan for rapid deployment. 7) Consider network segmentation to isolate the document management system from less secure network zones. 8) Educate users about the risks of credential sharing and phishing to reduce the likelihood of attacker authentication. These measures go beyond generic advice by focusing on authorization enforcement, monitoring, and access control tailored to this vulnerability’s exploitation vector.

Description

CVE-2026-1514 is a high-severity Incorrect Authorization vulnerability in the Official Document Management System by 2100 Technology, version 5.0.77. Authenticated remote attackers can exploit this flaw to modify front-end code, enabling unauthorized reading of all official documents. The vulnerability requires low attack complexity and no user interaction but does require attacker authentication with limited privileges. This can lead to significant confidentiality breaches, especially in organizations handling sensitive or classified documents. No known exploits are currently in the wild, but the impact on document confidentiality is critical. European organizations using this system should prioritize patching or implementing strict access controls. Countries with high adoption of 2100 Technology products and significant government or enterprise document management needs are at greater risk. Mitigation involves enforcing strict authorization checks, monitoring front-end code integrity, and restricting access to trusted users only.

Impact

For European organizations, the impact of CVE-2026-1514 is substantial due to the potential exposure of sensitive official documents. Confidentiality breaches could lead to data leaks involving government policies, legal documents, or corporate intellectual property. This could result in reputational damage, regulatory penalties under GDPR for data protection failures, and loss of trust among stakeholders. The ability of attackers to modify front-end code to bypass authorization controls means that even users with limited privileges can escalate their access, increasing insider threat risks. Organizations in sectors such as public administration, defense, legal, and finance are particularly vulnerable. The breach of official documents could also have geopolitical implications if sensitive diplomatic or security-related documents are exposed. Since the vulnerability requires authentication, insider threats or compromised credentials could be leveraged to exploit this flaw. The absence of known exploits currently provides a window for proactive defense, but the high severity score indicates urgent attention is needed to prevent future exploitation.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 09:30 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats