Cross-user record takeover via forged ownership fields
Published Aug 27, 2026 · Updated Aug 27, 2026
Authorization bypass in JEM before 5.0.1 allows remote authenticated users to take over other users' events and venues via forged form data. The event and venue edit path trusts the submitted record ID and created_by value instead of verifying that the record belongs to the requester. A registered account with edit-own rights through eventowner=1 or core.edit.own is sufficient, and the resulting access is limited to ownership and modification of those records.
Summary
What happened
Authorization bypass in JEM before 5.0.1 allows remote authenticated users to take over other users' events and venues via forged form data. The event and venue edit path trusts the submitted record ID and created_by value instead of verifying that the record belongs to the requester. A registered account with edit-own rights through eventowner=1 or core.edit.own is sufficient, and the resulting access is limited to ownership and modification of those records.
The record
- CVE
- CVE-2026-77035
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- JEM Team
- Product
- JEM
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 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=1.0.0-5.0.0
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