The Eventin WordPress plugin before 4.1.21 does not properly verify ownership of events before allowing them to be modified, deleted, or reassigned to a different author, allowing users with contributor-level access and above to alter, delete, or take over events created by other users including administrators.
CVE-2026-13169
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.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
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026Eventin < 4.1.21 – Contributor+ Arbitrary Event Modification, Deletion and Ownership Takeover via IDOR | CVE 2026-13169 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/cf2b1152-7190-467b-a860-1f7bd806575d/Vendor Advisories for CVE-2026-13169(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 13× in last 7d / 13× 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-21 00:53 UTCEG score recompute
- 2026-08-21 00:53 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:04 UTCGHSA enrichment
- 2026-08-20 01:08 UTCEG score recompute
- 2026-08-20 01:08 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:19 UTCEG score recompute▲ 8.10
- 2026-08-19 13:19 UTCGHSA enrichment
- 2026-08-19 13:17 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
- 2026-08-19 06:21 UTCNVD update
- 2026-08-19 06:18 UTCEG score recompute
- 2026-08-19 06: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-13169?
When was CVE-2026-13169 disclosed?
Is CVE-2026-13169 actively exploited?
What is the CVSS score of CVE-2026-13169?
How do I remediate CVE-2026-13169?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13169
Is Your Infrastructure Affected by CVE-2026-13169?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.