CVE-2026-111608

Published: Ott 16, 2026 Last Modified: Ott 16, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,3
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
MEDIUM 4,2
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: none
Integrity: low
Availability: low

Description

AI Translation Available

Jeepay through 3.2.9 contains an insecure direct object reference vulnerability that allows authenticated merchant users to delete other merchants' division receivers by exploiting an ownership check on the wrong column. Attackers holding ENT_DIVISION_RECEIVER_DELETE who own a receiver group whose id matches a victim's receiver id can delete the victim's profit-sharing receiver.

EPSS (Exploit Prediction Scoring System)

Trend Analysis

EPSS (Exploit Prediction Scoring System)

Prevede la probabilità di sfruttamento basata su intelligence sulle minacce e sulle caratteristiche della vulnerabilità.

EPSS Score
0,0025
Percentile
0,1th
Updated

EPSS Score Trend (Last 3 Days)

639

Authorization Bypass Through User-Controlled Key

Incomplete
Common Consequences
Security Scopes Affected:
Access Control
Potential Impacts:
Bypass Protection Mechanism Gain Privileges Or Assume Identity
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/jeequan/jeepay/blob/V3.2.9/jeepay-merchant/src/main/java/com…
https://hackmd.io/@hieuPenguinnn/jeepay-mch-payconfig-write-and-division-receiv…
https://www.vulncheck.com/advisories/jeepay-through-3.2.9-idor-via-delete-api-d…