CVE-2026-37149

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

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

GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0 was discovered to contain a SQL injection vulnerability in the scost parameter in /grocery/search_products.php. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.

CVSS v3
7.7
EG Score
7.7(high)
EPSS
11.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (3)

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

SQL Injection | OWASP Foundation

https://owasp.org/www-community/attacks/SQL_Injection
generic🟡 PoC Available

GitHub - pateldhyeyit/CVE-2026-37149: CVE-2026-37149 - SQL Injection vulnerability in the scost parameter of search_products.php in GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0. · GitHub

https://github.com/pateldhyeyit/CVE-2026-37149
generic

GitHub - anirudhkannanvp/GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN-: This project contains my project work on a grocery store management system done on PHP and MYSQL using XAMPP AND PHPMYADMIN · GitHub

https://github.com/anirudhkannanvp/GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN-

Vendor Advisories for CVE-2026-37149(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 33× in last 7d / 48× 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.

  1. 2026-07-07 01:52 UTCEG score recompute
  2. 2026-07-07 01:52 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:13 UTCEG score recompute
  6. 2026-07-06 13:13 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:25 UTCEG score recompute
  10. 2026-07-06 00:25 UTCGHSA enrichment
  11. 2026-07-05 11:46 UTCEG score recompute
  12. 2026-07-05 11:46 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 23:07 UTCEG score recompute
  15. 2026-07-04 23:07 UTCGHSA enrichment
  16. 2026-07-04 10:29 UTCEG score recompute
  17. 2026-07-04 10:29 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 21:48 UTCEG score recompute
  20. 2026-07-03 21:48 UTCGHSA enrichment
  21. 2026-07-03 09:09 UTCEG score recompute
  22. 2026-07-03 09:09 UTCGHSA enrichment
  23. 2026-07-02 20:30 UTCEG score recompute
  24. 2026-07-02 20:30 UTCGHSA enrichment
  25. 2026-07-02 07:52 UTCEG score recompute
Show 23 more
  1. 2026-07-02 07:52 UTCGHSA enrichment
  2. 2026-07-01 19:12 UTCEG score recompute
  3. 2026-07-01 19:12 UTCGHSA enrichment
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 06:34 UTCEG score recompute
  6. 2026-07-01 06:34 UTCGHSA enrichment
  7. 2026-06-30 17:55 UTCEG score recompute
  8. 2026-06-30 17:55 UTCGHSA enrichment
  9. 2026-06-30 05:16 UTCEG score recompute
  10. 2026-06-30 05:16 UTCGHSA enrichment
  11. 2026-06-29 16:38 UTCEG score recompute
  12. 2026-06-29 16:38 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 04:00 UTCEG score recompute
  15. 2026-06-29 03:59 UTCGHSA enrichment
  16. 2026-06-28 15:17 UTCEG score recompute▲ 7.70
  17. 2026-06-28 15:17 UTCGHSA enrichment
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 15:40 UTCNVD updateCVSS v3 → 7.7 · severity → HIGH
  22. 2026-06-25 21:46 UTCEG score recompute
  23. 2026-06-25 21:46 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCpateldhyeyit/CVE-2026-37149
    First seen Jun 20, 2026

    CVE-2026-37149 - SQL Injection vulnerability in the scost parameter of search_products.php in GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-37149?
CVE-2026-37149 is a high vulnerability published on June 25, 2026. GROCERY-STORE-MANAGEMENT-SYSTEM-USING-PHP-AND-MYSQL-PHPMYADMIN v1.0 was discovered to contain a SQL injection vulnerability in the scost parameter in /grocery/search_products.php. This vulnerability allows attackers to access sensitive database information via a crafted SQL statement.
When was CVE-2026-37149 disclosed?
CVE-2026-37149 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-37149 actively exploited?
CVE-2026-37149 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-37149?
CVE-2026-37149 has a CVSS v3.1 base score of 7.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-37149?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-37149, 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-2026-37149

Explore →

Is Your Infrastructure Affected by CVE-2026-37149?

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

Start Free Scan →Browse All CVEs