Cross-organizer event modification via mismatched authorization check
Published Aug 25, 2026 · Updated Aug 27, 2026
Broken access control in TYPO3 Events 2 10.0.0 through 10.2.11 allows remote authenticated users to modify other organizers' events. The frontend management update flow checks permission against one event identifier but applies changes to a different, user-selected event. Frontend event management access is required, and exploitation changes another organizer's event data without granting broader administrative control.
Summary
What happened
Broken access control in TYPO3 Events 2 10.0.0 through 10.2.11 allows remote authenticated users to modify other organizers' events. The frontend management update flow checks permission against one event identifier but applies changes to a different, user-selected event. Frontend event management access is required, and exploitation changes another organizer's event data without granting broader administrative control.
The record
- CVE
- CVE-2026-77145
- Published
- Aug 25, 2026
- Updated
- Aug 27, 2026
- Vendor
- in2code GmbH
- Product
- Events 2
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <8.6.3
- Affected versionversion=10.0.0 <10.2.12
- Affected versionversion=9.0.0 <9.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo