CVE-2026-105098
Received Received - Intake

Information Disclosure in Omega Solution CoinEx Crypto 2025

Publication date: 2026-10-04

Last updated on: 2026-10-04

Assigner: VulDB

Description
A security flaw has been discovered in Omega Solution CoinEx Crypto 2025. Affected is an unknown function of the file /ticket/customer of the component Support Ticket API. The manipulation of the argument status/page/count results in information disclosure. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks. The product web site does not exist anymore. Maybe the product got retired and/or replaced. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-04
Last Modified
2026-10-04
Generated
2026-10-04
AI Q&A
2026-10-04
EPSS Evaluated
N/A
NVD
CVE-2026-105098
EUVD
EUVD-2026-92066

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
omega coinex_crypto 2025

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an information disclosure flaw in Omega Solution CoinEx Crypto 2025. The issue occurs in the Support Ticket API endpoint /ticket/customer where manipulating the status/page/count arguments exposes sensitive data like bcrypt password hashes and internal account metadata such as user IDs, role IDs, and authentication flags. The API returns excessive data beyond what is necessary, violating least privilege principles.

Detection Guidance

To detect this vulnerability, inspect network traffic for requests to the GET /ticket/customer endpoint in Omega CoinEx Crypto. Look for responses containing excessive customer data like bcrypt hashes, user IDs, or role IDs. Use tools like curl to manually query the endpoint and check for sensitive fields in responses.

Impact Analysis

Attackers can remotely exploit this to access sensitive customer data including password hashes. This could lead to unauthorized account access, potential offline password cracking attacks, and exposure of internal system details like user roles and authentication status. The public availability of exploit code increases the risk of real-world attacks.

Compliance Impact

This vulnerability likely violates GDPR's data minimization principle and HIPAA's safeguards for protected health information by exposing excessive personal data. Organizations using this software may face compliance violations, regulatory fines, and increased risk of data breach notifications due to unauthorized data exposure.

Mitigation Strategies

Immediately restrict access to the /ticket/customer endpoint. Update the API to filter responses and only return necessary fields like customer ID, name, and profile image. Implement response DTOs or serializers to whitelist safe data. Consider disabling the endpoint if not critical.

Chat Assistant

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

EPSS Chart