Quick answers
- Is CVE-2026-13172 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13172 being exploited in the wild.
- How severe is CVE-2026-13172?
- Medium severity, with a CVSS score of 5.3, published 26 August 2026.
- Which products and versions are affected?
- Eventin Eventin before 4.1.22.
- Is there a fix for CVE-2026-13172?
- A patch was published on 2026-08-26: Fixed in version 4.1.22 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-13172 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-13172?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a broken access control issue (CWE-862) in the Eventin plugin's REST API endpoints (specifically the eventin/v1/event namespace). The plugin fails to validate user authorization or content status before serving event data via REST calls. An unauthenticated attacker can obtain a REST nonce from any public page and use it to query endpoints like /wp-json/eventin/v1/event/events and /wp-json/eventin/v1/event/seatmap_details to retrieve password-protected event content (including plaintext passwords), draft posts, pending posts, and private posts belonging to other users. This bypasses WordPress's native content access controls. The vulnerability was partially patched in versions 4.1.20–4.1.21 but fully fixed in version 4.1.22.
Affected products
- Eventin Eventin before 4.1.22
Timeline
- 2026-08-24: disclosed
- 2026-08-26: patched: Fixed in version 4.1.22