Skip to main content

CoinEx Crypto EUVDEUVD-2026-92063

| CVE-2026-105097 LOW
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-04 VulDB GHSA-v3m5-f97j-j2pm
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain low-privilege account
  2. Delivery
    Authenticate to Customer Information API
  3. Exploit
    Enumerate ID values on /customer-currency/
  4. Execution
    Server returns other customers' currency data
  5. Impact
    Harvest cross-account information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Exploitation requires the attacker to already hold a valid low-privilege authenticated account (PR:L) on a CoinEx Crypto 2025 deployment and to reach the Customer Information API endpoint /customer-currency/ over the network; the attacker manipulates the user-controlled 'ID' argument to reference records they do not own. The limiting factors are: valid authentication is mandatory (not anonymous), impact is confined to reading another customer's currency data (no modification or service disruption), and the realistic exposure is minimal because the product is apparently retired with no live vendor presence - so few if any instances remain in production. No special non-default configuration is indicated; the flaw appears present in the standard API behavior.

Impact

This is a textbook moderate-severity IDOR (CWE-639, authorization bypass through a user-controlled 'ID' key) in the Customer Information API endpoint /customer-currency/ of Omega Solution's CoinEx Crypto 2025. The vendor-assigned CVSS 4.0 vector (AV:N/AC:L/PR:L/UI:N, VC:L with no integrity or availability impact, E:P) scores 5.3 and aligns with the description: a network-reachable, low-complexity flaw that requires an existing low-privilege authenticated account (PR:L) and yields only limited confidentiality exposure (one customer reading another customer's currency records). Exploitation signals are mixed: a public PoC exists (publicly available exploit code exists), but there is NO CISA KEV listing and NO EPSS score was provided, so there is no evidence of active or widespread exploitation - the PoC raises accessibility, not confirmed in-the-wild use. Critically, the product website no longer exists and the product is likely retired/replaced, and the vendor did not respond to disclosure, meaning no patch is available or expected. Net assessment: real but low-priority. The combination of authentication requirement, confidentiality-only impact, likely tiny/retired deployment base, and absence of KEV/EPSS signals indicates a genuine-but-niche issue rather than an urgent threat - far below a 'high CVSS but low real risk' panic case, and more accurately a 'low-everything' case.

Exploit ScenarioDerived

An attacker who holds any valid low-privilege customer account on a CoinEx Crypto 2025 instance sends a request to /customer-currency/ while manipulating the 'ID' parameter to reference another customer's identifier. Because the endpoint does not verify object ownership, it returns that other customer's currency information, disclosing data across account boundaries. A public proof-of-concept for this IDOR is available on GitHub, lowering the skill needed to reproduce it.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 04, 2026

Authorization bypass (IDOR) in Omega Solution's CoinEx Crypto 2025 allows an authenticated low-privilege user to read other customers' currency records by tampering with the 'ID' argument on the Customer Information API endpoint /customer-currency/. Exploitation is remote, requires a valid low-privilege account, and yields limited confidentiality impact only - no data modification or service disruption (CVSS 3.1 5.3/5.3, PR:L, C:L). Publicly available exploit code exists (a VulDB PoC referenced on GitHub), but there is no confirmation of active exploitation in the wild, and realistic exposure is minimal because the product appears retired with no functioning vendor site and an unresponsive vendor.

RemediationAI

No vendor-released patch has been identified for this CVE: the vendor did not respond to the disclosure, the product web site is gone, and no fixed version, commit, or upgrade path appears in any reference - so plan for compensating controls rather than an upgrade. The most effective control is a server-side authorization fix in the Customer Information API: never trust the client-supplied 'ID'; instead derive the customer/account scope from the authenticated session and reject or silently scope any request whose 'ID' is not owned by that principal, and validate the parameter as an integer within an allow-listed range. If code cannot be changed, network- or gateway-layer mitigations are the next best option: block or restrict external access to /customer-currency/ (and the Customer Information API generally) so only trusted internal callers or admin networks can reach it - trade-off is loss of that functionality for legitimate remote users. Alternatively, force re-authentication or step-up verification for that endpoint, or reduce the privilege/scope of issued low-privilege tokens and rotate existing ones so old tokens can no longer enumerate records - trade-off is operational churn and possible breakage of integrations. A WAF rule that rejects requests with unexpected or sequentially enumerated 'ID' values can raise the cost of mass enumeration but is trivially bypassable with non-sequential IDs and should not be relied on alone. Finally, since the product is apparently retired, prioritize decommissioning remaining CoinEx Crypto 2025 instances or isolating them on a segmented network with no route to customer data stores; if any instance must stay live, enable and forward access logs for /customer-currency/ to detect enumeration patterns, and treat any data already exposed as requiring customer notification review given the demonstrated public PoC.

Affected VersionsENISA

CoinEx Crypto 2025

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-639, Authorization Bypass Through User-Controlled Key - the classic Insecure Direct Object Reference (IDOR) pattern. The Customer Information API exposes a resource route (/customer-currency/) that accepts a client-supplied 'ID' parameter and uses it directly to select a database record without verifying that the record belongs to the authenticated principal making the request. Because the server trusts the object identifier rather than scoping the query to the session's own user or tenant, any holder of a valid low-privilege token can substitute an arbitrary ID and retrieve another customer's currency information. Note the nuance versus the tag 'Authentication Bypass': this is not a credential or session bypass - authentication is still required (CVSS PR:L) - it is a horizontal privilege-escalation/access-control failure that weakens attribute confidentiality only (VC:L, no VI/VA). The CPE entry cpe:2.3:a:omega_solution:coinex_crypto:*:*:*:*:*:*:*:* carries a wildcard version, indicating the vendor never enumerated affected releases, which is consistent with an apparently abandoned/retired product line. Only VulDB-derived references exist (advisory 413346, its CTI page, and the CVE record), with no vendor security advisory, changelog, or patch commit - a strong signal of a product with no active maintenance.

Know when Coinex Crypto gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
vuln.today AI 4.3 MEDIUM

Network-reachable IDOR needing a low-privilege account (PR:L, AC:L); it discloses another user's data (C:L) but allows no modification or disruption (I:N/A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 04, 2026 - 03:22 NVD
MEDIUM LOW
CVSS changed
Oct 04, 2026 - 03:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 04, 2026 - 02:00 cve.org
MEDIUM 5.3

DescriptionCVE.org

A vulnerability was identified in Omega Solution CoinEx Crypto 2025. This impacts an unknown function of the file /customer-currency/ of the component Customer Information API. The manipulation of the argument ID leads to authorization bypass. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. 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.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Rare
obscure vendor, product retired and website no longer exists
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in Omega Solution CoinEx Crypto API Vulnerabilities

View all 3

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy