CVE-2026-92366

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-16. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.3Exploit: Elevated riskExposed: 0

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

A vulnerability was determined in code-projects Matrimonial System 1.0. This affects an unknown part of the file /search.php of the component Regular Search. This manipulation of the argument sex/mothertongue/maritialstatus/country/state/religion/agemin/agemax causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

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 computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

References (15)

Vendor Advisories for CVE-2026-92366(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 42× 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-09-25 02:00 UTCEG score recompute
  2. 2026-09-25 02:00 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 12:55 UTCGHSA enrichment
  5. 2026-09-23 23:49 UTCEG score recompute
  6. 2026-09-23 23:49 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 10:45 UTCGHSA enrichment
  9. 2026-09-22 21:34 UTCEG score recompute
  10. 2026-09-22 21:34 UTCGHSA enrichment
  11. 2026-09-22 16:01 UTCEPSS rescore
  12. 2026-09-22 08:30 UTCEG score recompute
  13. 2026-09-22 08:30 UTCGHSA enrichment
  14. 2026-09-21 21:09 UTCEPSS rescore
  15. 2026-09-21 19:24 UTCGHSA enrichment
  16. 2026-09-21 06:19 UTCEG score recompute
  17. 2026-09-21 06:19 UTCGHSA enrichment
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-20 17:14 UTCGHSA enrichment
  20. 2026-09-20 04:09 UTCEG score recompute
  21. 2026-09-20 04:09 UTCGHSA enrichment
  22. 2026-09-19 15:04 UTCGHSA enrichment
  23. 2026-09-19 01:56 UTCEG score recompute
  24. 2026-09-19 01:55 UTCGHSA enrichment
  25. 2026-09-18 19:28 UTCEPSS rescore
Show 17 more
  1. 2026-09-18 12:50 UTCGHSA enrichment
  2. 2026-09-17 23:45 UTCEG score recompute
  3. 2026-09-17 23:44 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 10:06 UTCGHSA enrichment
  6. 2026-09-16 21:00 UTCEG score recompute
  7. 2026-09-16 21:00 UTCGHSA enrichment
  8. 2026-09-16 20:25 UTCNVD updateCVSS v4 → 5.5
  9. 2026-09-16 19:34 UTCEG score recompute
  10. 2026-09-16 19:34 UTCGHSA enrichment
  11. 2026-09-16 19:34 UTCMITRE cvelistV5CVSS v4 → 6.9
  12. 2026-09-16 18:03 UTCEG score recompute
  13. 2026-09-16 18:03 UTCGHSA enrichment
  14. 2026-09-16 15:23 UTCEG score recompute
  15. 2026-09-16 15:23 UTCNVD updateCVSS v4 → 5.5
  16. 2026-09-16 14:26 UTCEG score recompute
  17. 2026-09-16 14:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-92366?
CVE-2026-92366 is a high vulnerability published on September 16, 2026. A vulnerability was determined in code-projects Matrimonial System 1.0. This affects an unknown part of the file /search.php of the component Regular Search. This manipulation of the argument sex/mothertongue/maritialstatus/country/state/religion/agemin/agemax causes sql injection. The attack can…
When was CVE-2026-92366 disclosed?
CVE-2026-92366 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92366 actively exploited?
CVE-2026-92366 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.7% of all scored CVEs.
What is the CVSS score of CVE-2026-92366?
CVE-2026-92366 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-92366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92366, 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-92366

Explore →

Is Your Infrastructure Affected by CVE-2026-92366?

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

Book a Demo →Browse All CVEs