FreeSMS 2.1.2 Login Endpoint crc_handler.php?method=login sql injection

Summaryinfo

A vulnerability was found in FreeSMS 2.1.2. It has been rated as critical. Affected by this issue is some unknown functionality of the file /pages/crc_handler.php?method=login of the component Login Endpoint. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2019-25506. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in FreeSMS 2.1.2. This affects an unknown function of the file /pages/crc_handler.php?method=login of the component Login Endpoint. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

FreeSMS 2.1.2 contains a boolean-based blind SQL injection vulnerability in the password parameter that allows unauthenticated attackers to bypass authentication by injecting SQL code through the login endpoint. Attackers can exploit the vulnerable password parameter in requests to /pages/crc_handler.php?method=login to authenticate as any known user and subsequently modify their password via the profile update function.

The weakness was shared by Yilmaz Degirmenci as 46658. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25506 since 03/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• FreeSMS

Version

• 2.1.2

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion