CVE-2026-2093VulnerabilityPublished 10 Feb 2026

CVE-2026-2093: Flowring Docpedia · SQL Injection

Affects Flowring DocpediaSource CVE Database V5

Not known to be exploited · CVSS 8.7 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

8.7High

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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 10 Feb 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 2026-10-25.

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
FlowringDocpedia	Affected =3.0	Fixed in–

AI-suggested

1. Monitor Flowring's official channels for patches addressing CVE-2026-2093 and apply them immediately upon release. 2. Until patches are available, deploy Web Application Firewalls (WAFs) with SQL Injection detection and prevention rules tailored to Docpedia's traffic patterns. 3. Conduct a thorough code review of all database interaction points in Docpedia installations to identify and remediate unsafe SQL query constructions, replacing them with parameterized queries or prepared statements. 4. Restrict database user permissions to the minimum necessary to limit the impact of any injection attack. 5. Implement network segmentation and access controls to limit exposure of Docpedia servers to untrusted networks. 6. Enable detailed logging and monitoring of database queries and application logs to detect suspicious activities indicative of injection attempts. 7. Educate development and security teams on secure coding practices to prevent similar vulnerabilities in future releases. 8. Consider temporary disabling or restricting access to vulnerable Docpedia instances if critical data exposure risk is unacceptable and no immediate patch is available.

Description

CVE-2026-2093 is a high-severity SQL Injection vulnerability in Flowring's Docpedia version 3.0. It allows unauthenticated remote attackers to inject arbitrary SQL commands, potentially exposing sensitive database contents without requiring any user interaction or privileges. The vulnerability stems from improper neutralization of special elements in SQL commands (CWE-89). Although no known exploits are currently reported in the wild, the ease of exploitation and the critical impact on confidentiality make this a significant threat. European organizations using Docpedia 3.0 are at risk of data breaches and unauthorized data disclosure. Immediate mitigation involves applying patches once available, implementing web application firewalls with SQLi detection, and auditing database query handling. Countries with higher adoption of Flowring Docpedia, especially those with critical infrastructure or sensitive data managed via this product, are more likely to be targeted. Given the CVSS 4.

Impact

For European organizations, exploitation of this vulnerability could lead to significant data breaches, exposing sensitive personal data protected under GDPR, intellectual property, or operational information. Unauthorized database access can compromise confidentiality and potentially integrity if attackers modify data. This could result in regulatory penalties, reputational damage, and operational disruptions. Sectors such as finance, healthcare, government, and critical infrastructure that may use Docpedia for document management or knowledge bases are particularly at risk. The vulnerability's unauthenticated nature means attackers can exploit it remotely without insider access, increasing the threat surface. Additionally, data leakage could facilitate further attacks such as phishing or social engineering. The absence of known exploits currently provides a window for proactive defense, but the high CVSS score indicates that once exploited, the impact could be severe.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
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.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (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 17 Feb 2026, 09:32 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats