CVE-2026-82879
Received Received - Intake

DataEase Access Control Bypass via Share Ticket Manipulation

Publication date: 2026-08-31

Last updated on: 2026-08-31

Assigner: VulnCheck

Description
DataEase before 2.10.26 contains multiple access control defects in the sharing link module. Tickets are not bound to the target share UUID, so a valid ticket issued for one share can be reused against another (ShareTicketManage.validateTicket / POST /de2api/share/proxyInfo). The POST /de2api/share/validate endpoint issues a LinkToken after password verification without requiring a ticket, bypassing the 'ticket mandatory' policy. Additionally, the ticket create and delete endpoints (POST /de2api/ticket/saveTicket, POST /de2api/ticket/delTicket) lack share-ownership checks, allowing an authenticated user who knows another user's ticket to modify, rebind, or delete it (denial of service), and GET /de2api/share/queryRelationByUserId/{uid} allows authenticated users to enumerate other users' share mappings.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-31
Last Modified
2026-08-31
Generated
2026-08-31
AI Q&A
2026-08-31
EPSS Evaluated
N/A
NVD
CVE-2026-82879
EUVD
EUVD-2026-68465

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
dataease dataease to 2.10.26 (exc)
fit2cloud dataease to 2.10.26 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

DataEase before version 2.10.26 has multiple access control flaws in its sharing link module. Tickets are not properly linked to specific shares, allowing a valid ticket for one share to be reused on another. The system also allows bypassing ticket requirements by generating a LinkToken without proper validation. Ticket creation and deletion endpoints lack ownership checks, enabling unauthorized users to modify or delete others' tickets. Additionally, an endpoint allows enumeration of other users' share mappings.

Detection Guidance

To detect this vulnerability, check if your DataEase instance is running a version prior to 2.10.26. Use system commands like 'curl -X GET http://<target>/de2api/share/queryRelationByUserId/{uid}' to test for share mapping enumeration. Verify if ticket reuse is possible by attempting to access different shares with the same ticket. Check for unauthorized ticket modifications via POST requests to /de2api/ticket/saveTicket or /de2api/ticket/delTicket without proper ownership validation.

Inspect network traffic for POST /de2api/share/validate requests that issue LinkToken without ticket validation. Monitor logs for repeated failed access attempts or unusual ticket operations. Ensure all endpoints enforce UUID binding and ownership checks as described in the patched version.

Impact Analysis

An attacker with an authenticated session could access unauthorized shares by reusing tickets, bypass password requirements, manipulate or delete others' tickets causing denial of service, or identify target shares through enumeration. This could lead to unauthorized data access or disruption of shared resources.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating confidentiality requirements in GDPR and HIPAA. The lack of proper access controls may result in non-compliance with data protection principles, potentially leading to regulatory penalties or data breaches.

Mitigation Strategies

Immediately upgrade DataEase to version 2.10.26 or later to address all identified access control defects. Disable or restrict access to the vulnerable endpoints if an upgrade is not immediately feasible. Implement strict input validation for UUIDs and enforce ownership checks on all ticket-related operations.

Review and revoke any potentially compromised tickets. Monitor for unauthorized access attempts or ticket manipulations. Apply network-level controls to limit exposure of the affected endpoints until patches are applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82879. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart