An improper authorization vulnerability in Attendize through commit 9289acb allows an authenticated remote attacker to inject persistent mandatory survey questions into another organizer's events via the POST /event/{event_id}/question/create endpoint. The postCreateEventQuestion method loads the target event without the tenant-isolation scope, enabling cross-tenant writes; the injected question cannot be removed by the victim because the victim's account-scoped delete path cannot resolve a question owned by another tenant.
CVE-2026-72690
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 10, 2026
Advisory Details (1)
Auto-updated Aug 10, 2026GitHub - Attendize/Attendize: Attendize is an open-source ticket selling and event management platform built on Laravel. · GitHub
https://github.com/Attendize/AttendizeVendor Advisories for CVE-2026-72690(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 31× in last 7d / 51× 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.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 22:22 UTCGHSA enrichment
- 2026-08-20 10:51 UTCGHSA enrichment
- 2026-08-19 23:20 UTCEG score recompute
- 2026-08-19 23:20 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 11:49 UTCGHSA enrichment
- 2026-08-19 00:17 UTCEG score recompute
- 2026-08-19 00:17 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 12:46 UTCGHSA enrichment
- 2026-08-18 00:28 UTCEG score recompute
- 2026-08-18 00:27 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:48 UTCGHSA enrichment
- 2026-08-17 01:17 UTCEG score recompute
- 2026-08-17 01:17 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:46 UTCEG score recompute
- 2026-08-16 13:46 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-16 02:15 UTCGHSA enrichment
- 2026-08-15 14:44 UTCGHSA enrichment
Show 26 moreShow fewer
- 2026-08-15 03:13 UTCEG score recompute
- 2026-08-15 03:13 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 15:41 UTCGHSA enrichment
- 2026-08-14 04:10 UTCEG score recompute
- 2026-08-14 04:10 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 16:39 UTCGHSA enrichment
- 2026-08-13 05:04 UTCGHSA enrichment
- 2026-08-12 17:34 UTCEG score recompute
- 2026-08-12 17:34 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 06:02 UTCGHSA enrichment
- 2026-08-11 18:31 UTCEG score recompute
- 2026-08-11 18:31 UTCGHSA enrichment
- 2026-08-11 06:59 UTCGHSA enrichment
- 2026-08-10 19:28 UTCEG score recompute
- 2026-08-10 19:28 UTCGHSA enrichment
- 2026-08-10 19:26 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
- 2026-08-10 18:35 UTCEG score recompute
- 2026-08-10 18:35 UTCGHSA enrichment
- 2026-08-10 18:34 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
- 2026-08-10 13:28 UTCEG score recompute▲ 1.70
- 2026-08-10 13:24 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
- 2026-08-10 12:17 UTCEG score recompute
- 2026-08-10 12:17 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-72690?
When was CVE-2026-72690 disclosed?
Is CVE-2026-72690 actively exploited?
What is the CVSS score of CVE-2026-72690?
How do I remediate CVE-2026-72690?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72690
Is Your Infrastructure Affected by CVE-2026-72690?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.