CVE-2018-25362

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. 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.

Twitter-Clone 1 contains a SQL injection vulnerability in follow.php that allows attackers to manipulate database queries by injecting SQL code through the userid parameter. Attackers can submit union-based or time-based blind SQL injection payloads to extract sensitive database information including usernames, passwords, and database credentials.

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

Published

May 25, 2026

Last Modified

May 26, 2026

Advisory Details (3)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Twitter-Clone 1 SQL Injection via follow.php | Advisories | VulnCheck

https://www.vulncheck.com/advisories/twitter-clone-1-sql-injection-via-follow-php
generic🟡 PoC Available

Twitter-Clone 1 - 'userid' SQL Injection - PHP webapps Exploit

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

GitHub - Fyffe/PHP-Twitter-Clone: Twitter clone made in PHP. · GitHub

https://github.com/Fyffe/PHP-Twitter-Clone/

Vendor Advisories for CVE-2018-25362(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 70× 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 163 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-25362?
CVE-2018-25362 is a high vulnerability published on May 25, 2026. Twitter-Clone 1 contains a SQL injection vulnerability in follow.php that allows attackers to manipulate database queries by injecting SQL code through the userid parameter. Attackers can submit union-based or time-based blind SQL injection payloads to extract sensitive database information…
When was CVE-2018-25362 disclosed?
CVE-2018-25362 was first published in the National Vulnerability Database on May 25, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-25362 actively exploited?
CVE-2018-25362 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-25362?
CVE-2018-25362 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2018-25362?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-25362, 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-2018-25362

Explore →

Is Your Infrastructure Affected by CVE-2018-25362?

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

Start Free Scan →Browse All CVEs