Overview
Today we’ll be discussing an alarming vulnerability in Touch Lebanon Mobile App version 2.20.2, identified as CVE-2025-50503. This vulnerability allows an attacker to bypass the One-Time-Password (OTP) mechanism during the password reset workflow, enabling unauthorized access to user accounts. The potential impact is severe, as it directly compromises the security of user accounts, opening the door for potential system compromise or data leakage. This vulnerability concerns any individual or entity using the specified version of the Touch Lebanon Mobile App, emphasizing the critical importance of swift mitigation.
Vulnerability Summary
CVE ID: CVE-2025-50503
Severity: Critical (8.8 CVSS v3)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: Unauthorized access to user accounts, potential system compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Touch Lebanon Mobile App | 2.20.2
How the Exploit Works
The vulnerability lies in the password reset workflow of the app. After a user initiates a password reset, they receive an OTP for authentication. However, an attacker can manipulate the reset process to bypass this OTP validation. The exact technical details of this manipulation cannot be disclosed due to security reasons, but it involves a sequence of actions that intercept and exploit the communication between the user and the server during the password reset process.
Conceptual Example Code
Here is a conceptual illustration of how the vulnerability might be exploited using an HTTP request. This example should not be used for malicious intent and is provided for educational purposes only.
POST /password-reset HTTP/1.1
Host: touchlebanonapp.com
Content-Type: application/json
{
"userID": "<victim's userID>",
"newPassword": "<attacker's chosen password>",
"otp": "<any value>"
}Under normal circumstances, the server should validate the “otp” value in the request against the OTP sent to the user. However, due to the vulnerability, the server does not validate this field, allowing the attacker to change the password of any user account.
Mitigation Guidance
Users are strongly advised to apply the vendor patch as soon as it becomes available. In the meantime, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can provide temporary mitigation by detecting and blocking suspicious activities. Additionally, it is always recommended to regularly monitor your accounts for any signs of unauthorized access or unusual activity.