# CVE-2019-25506: FreeSMS 2.1.2 Authentication Bypass via SQL Injection

> Unauthenticated attackers can bypass login via SQL injection to take over accounts and modify passwords in FreeSMS.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-j4rv-c327-frjj

## What is CVE-2019-25506?

CVE-2019-25506 is a high-severity SQL injection vulnerability in FreeSMS, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25506?

It affects 1 product.


Products: Freesms Project Freesms.

## How do I fix CVE-2019-25506?

No fix has been published for CVE-2019-25506 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25506 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25506 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25506 and fix it if it is affected.

What it is: CVE-2019-25506 is a high-severity SQL injection vulnerability in FreeSMS, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25506 exists.

Affected product: FreeSMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-25506/ (Markdown: https://insights.sbomify.com/CVE-2019-25506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25506
- OSV: https://osv.dev/vulnerability/CVE-2019-25506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-25506/
Summaries are generated and may contain mistakes; the official description above is the record.