Contributor-level code execution via event_layout file inclusion
Published Sep 9, 2026 · Updated Sep 9, 2026
Local file inclusion in Arraytics Eventin 4.1.22 and earlier allows remote authenticated users to execute PHP via event_layout. The REST event update path accepts an attacker-controlled event_layout value, and template rendering uses the resulting path in a PHP include without restricting it to approved templates. Contributor access is sufficient by default through etn_manage_event, but code execution requires an includable PHP file already present on the server.
Summary
What happened
Local file inclusion in Arraytics Eventin 4.1.22 and earlier allows remote authenticated users to execute PHP via event_layout. The REST event update path accepts an attacker-controlled event_layout value, and template rendering uses the resulting path in a PHP include without restricting it to approved templates. Contributor access is sufficient by default through etn_manage_event, but code execution requires an includable PHP file already present on the server.
The record
- CVE
- CVE-2026-15667
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- Arraytics
- Product
- Eventin
- Classifications
- CWE-98, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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 <=4.1.22
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