CVE-2019-25325

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-02-13. NVD baseline CVSS 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Thrive Smart Home 1.1 contains an SQL injection vulnerability in the checklogin.php endpoint that allows unauthenticated attackers to bypass authentication by manipulating the 'user' POST parameter. Attackers can inject malicious SQL code like ' or 1=1# to manipulate login queries and gain unauthorized access to the application.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
25.0%
KEV
Not listed

Published

February 12, 2026

Last Modified

April 15, 2026

Advisory Details (5)

Auto-updated Jun 8, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🔴 Active Exploitation

Zero Science Lab — Information Security Research & Development Laboratory

https://www.zeroscience.mk/en/vulnerabilities/ZSL-2019-5554.php
generic🟡 PoC Available

Thrive Smart Home 1.1 - Authentication Bypass - PHP webapps Exploit

https://www.exploit-db.com/exploits/47814
generic

Packet Storm

https://packetstorm.news/files/id/155797
generic

IBM X-Force Exchange

https://exchange.xforce.ibmcloud.com/vulnerabilities/173728
generic

Thrive Smart Home 1.1 Authentication Bypass - CXSecurity.com

https://cxsecurity.com/issue/WLB-2020010019

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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.

Showing the most recent 100 of 131 total refreshes for this CVE.

  1. 2026-07-15 16:55 UTCEPSS rescore
  2. 2026-07-15 16:55 UTCEPSS rescore
  3. 2026-07-13 22:27 UTCEPSS rescore
  4. 2026-07-13 06:10 UTCEPSS rescore
  5. 2026-07-13 06:10 UTCEPSS rescore
  6. 2026-07-12 05:43 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-11 08:24 UTCEPSS rescore
  9. 2026-07-11 08:24 UTCEPSS rescore
  10. 2026-07-09 19:06 UTCEPSS rescore
  11. 2026-07-08 15:11 UTCEPSS rescore
  12. 2026-07-07 13:43 UTCEPSS rescore
  13. 2026-07-06 16:25 UTCEPSS rescore
  14. 2026-07-06 16:25 UTCEPSS rescore
  15. 2026-07-06 02:20 UTCEPSS rescore
  16. 2026-07-05 02:27 UTCEPSS rescore
  17. 2026-07-04 06:28 UTCEPSS rescore
  18. 2026-07-01 15:03 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-06-30 23:20 UTCEPSS rescore
  21. 2026-06-29 14:03 UTCEPSS rescore
  22. 2026-06-28 14:04 UTCEPSS rescore
  23. 2026-06-28 04:54 UTCEPSS rescore
  24. 2026-06-28 04:54 UTCEPSS rescore
  25. 2026-06-27 03:06 UTCEPSS rescore
Show 75 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-24 14:03 UTCEPSS rescore
  4. 2026-06-24 14:03 UTCEPSS rescore
  5. 2026-06-23 21:31 UTCEPSS rescore
  6. 2026-06-23 21:30 UTCEPSS rescore
  7. 2026-06-22 14:23 UTCEPSS rescore
  8. 2026-06-21 14:54 UTCEPSS rescore
  9. 2026-06-21 14:54 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-19 19:23 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-14 23:15 UTCEPSS rescore
  19. 2026-06-14 23:15 UTCEPSS rescore
  20. 2026-06-13 22:58 UTCEPSS rescore
  21. 2026-06-12 23:09 UTCEPSS rescore
  22. 2026-06-12 03:53 UTCEG score recompute
  23. 2026-06-12 03:53 UTCGHSA enrichment
  24. 2026-06-11 13:58 UTCEPSS rescore
  25. 2026-06-10 22:16 UTCEPSS rescore
  26. 2026-06-10 22:03 UTCEG score recompute
  27. 2026-06-10 22:03 UTCGHSA enrichment
  28. 2026-06-10 13:19 UTCEPSS rescore
  29. 2026-06-10 02:26 UTCEG score recompute
  30. 2026-06-10 02:26 UTCGHSA enrichment
  31. 2026-06-08 14:15 UTCEPSS rescore
  32. 2026-06-08 06:20 UTCEG score recompute
  33. 2026-06-08 06:20 UTCGHSA enrichment
  34. 2026-06-07 19:20 UTCEG score recompute
  35. 2026-06-07 19:20 UTCGHSA enrichment
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-07 15:23 UTCEPSS rescore
  38. 2026-06-06 13:45 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-05 22:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 06:08 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-04 13:10 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-02 20:11 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-05-31 22:29 UTCEPSS rescore
  51. 2026-05-31 22:29 UTCEPSS rescore
  52. 2026-05-31 00:14 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-29 13:42 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-26 13:42 UTCEPSS rescore
  58. 2026-05-26 13:42 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-22 21:16 UTCEPSS rescore
  63. 2026-05-22 21:16 UTCEPSS rescore
  64. 2026-05-22 21:16 UTCEPSS rescore
  65. 2026-05-22 21:16 UTCEPSS rescore
  66. 2026-05-22 21:16 UTCEPSS rescore
  67. 2026-05-22 21:16 UTCEPSS rescore
  68. 2026-05-22 21:16 UTCEPSS rescore
  69. 2026-05-22 21:15 UTCEPSS rescore
  70. 2026-05-22 21:15 UTCEPSS rescore
  71. 2026-05-22 21:15 UTCEPSS rescore
  72. 2026-05-21 22:40 UTCEPSS rescore
  73. 2026-05-21 22:40 UTCEPSS rescore
  74. 2026-05-21 22:40 UTCEPSS rescore
  75. 2026-05-20 23:01 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-25325?
CVE-2019-25325 is a high vulnerability published on February 12, 2026. Thrive Smart Home 1.1 contains an SQL injection vulnerability in the checklogin.php endpoint that allows unauthenticated attackers to bypass authentication by manipulating the 'user' POST parameter. Attackers can inject malicious SQL code like ' or 1=1# to manipulate login queries and gain…
When was CVE-2019-25325 disclosed?
CVE-2019-25325 was first published in the National Vulnerability Database on February 12, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25325 actively exploited?
CVE-2019-25325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-25325?
CVE-2019-25325 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2019-25325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25325, 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-25325

Explore →

Is Your Infrastructure Affected by CVE-2019-25325?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs