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.
CVE-2019-25506
CRITICALNVD 9.89.8Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
Triggered by: NVD CVSS baseline
Sources: ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(low)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
March 4, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026🔬 Proof of concept available. No patch confirmed yet.
generic
FreeSMS 2.1.2 Authentication Bypass via SQL Injection | Advisories | VulnCheck
https://www.vulncheck.com/advisories/freesms-authentication-bypass-via-sql-injectiongeneric🟡 PoC Available
FreeSMS 2.1.2 - SQL Injection (Authentication Bypass) - PHP webapps Exploit
https://www.exploit-db.com/exploits/46658Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-01 04:12 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:27 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-27 13:52 UTCEG score recompute
- 2026-07-27 13:52 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2019-25506?
CVE-2019-25506 is a critical vulnerability published on March 4, 2026. 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…
When was CVE-2019-25506 disclosed?
CVE-2019-25506 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25506 actively exploited?
CVE-2019-25506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.8% of all scored CVEs.
What is the CVSS score of CVE-2019-25506?
CVE-2019-25506 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2019-25506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25506, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-25506
Is Your Infrastructure Affected by CVE-2019-25506?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.