CVE-2026-92298

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

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

EspoCRM through 10.0.8 uses PHP's rand() function to generate tokens for lead-capture opt-in, event invitation, and campaign URLs instead of a cryptographically secure generator. Remote unauthenticated attackers can guess these roughly 31-bit tokens to confirm opt-ins, accept or decline event invitations on behalf of other contacts, and access event details.

CVSS v3
4.8
EG Score
4.8(high)
EG Risk
22(Track)
EG Risk 22/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 computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

EspoCRM through 10.0.8 Weak Token Generation via rand() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/espocrm-through-10.0.8-weak-token-generation-via-rand
generic

GitHub - espocrm/espocrm: EspoCRM – Open Source CRM Application · GitHub

https://github.com/espocrm/espocrm
generic

espocrm/application/Espo/Repositories/UniqueId.php at 10.0.8 · espocrm/espocrm · GitHub

https://github.com/espocrm/espocrm/blob/10.0.8/application/Espo/Repositories/UniqueId.php#L47
generic

espocrm/application/Espo/Core/Utils/Util.php at 10.0.8 · espocrm/espocrm · GitHub

https://github.com/espocrm/espocrm/blob/10.0.8/application/Espo/Core/Utils/Util.php#L585-L590
github_commit

commit 8e5555c1ee0e (espocrm/espocrm)

Fix landed in espocrm/espocrm commit 8e5555c1ee0e — awaiting tagged release

https://github.com/espocrm/espocrm/commit/8e5555c1ee0ed1e92a9ad54e62f735ac2c4051a1
generic

EspoCRM Security Vulnerabilities for CVE Assignment · GitHub

https://gist.github.com/kazisabu/9e3109aab24245fde19b88f53f965e93

Vendor Advisories for CVE-2026-92298(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 14× in last 7d / 14× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:47 UTCEG score recompute
  3. 2026-09-18 18:47 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 18:26 UTCEG score recompute
  6. 2026-09-17 18:26 UTCGHSA enrichment
  7. 2026-09-17 18:01 UTCEG score recompute
  8. 2026-09-17 18:00 UTCGHSA enrichment
  9. 2026-09-17 02:48 UTCEG score recompute
  10. 2026-09-17 02:48 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 02:25 UTCEG score recompute
  13. 2026-09-16 02:03 UTCEG score recompute
  14. 2026-09-16 02:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92298?
CVE-2026-92298 is a medium vulnerability published on September 16, 2026. EspoCRM through 10.0.8 uses PHP's rand() function to generate tokens for lead-capture opt-in, event invitation, and campaign URLs instead of a cryptographically secure generator. Remote unauthenticated attackers can guess these roughly 31-bit tokens to confirm opt-ins, accept or decline event…
When was CVE-2026-92298 disclosed?
CVE-2026-92298 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92298 actively exploited?
CVE-2026-92298 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 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-92298?
CVE-2026-92298 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-92298?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92298, 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-92298

Explore →

Is Your Infrastructure Affected by CVE-2026-92298?

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

Start Free Scan →Browse All CVEs