Quick answers
- Is CVE-2026-81802 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81802 being exploited in the wild.
- How severe is CVE-2026-81802?
- Medium severity, with a CVSS score of 6.5, published 8 September 2026.
- Which products and versions are affected?
- MagePeople WpEvently 5.6.0 and earlier.
- Is there a fix for CVE-2026-81802?
- A patch was published on 2026-09-07: Patched in version 5.6.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81802 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-81802?
- Check whether you run MagePeople WpEvently at an affected version. 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 an Insecure Direct Object References (IDOR) flaw in WpEvently versions up to 5.6.0 that does not properly validate authorization before exposing objects tied to user-controlled IDs. The vulnerability is unauthenticated, meaning an attacker does not need valid credentials to exploit it. By modifying ID parameters in API calls or URLs, an attacker can enumerate and access other users' event records, bookings, and potentially sensitive customer information. The vulnerability has been patched in version 5.6.4 and later.
Affected products
- MagePeople WpEvently 5.6.0 and earlier
Timeline
- 2026-09-07: disclosed
- 2026-09-07: patched: Patched in version 5.6.4
- 2026-08-30: other: Reported by benzdeus