Unauthenticated local file inclusion
Published Jun 16, 2026 · Updated Jun 16, 2026
Local file inclusion in ThemeREX Choreo 1.6 and earlier allows remote attackers to include local files without authentication. The public record does not identify the affected file, function, request parameter, or included-file constraint, so exact read or execution outcomes remain undisclosed.
Summary
What happened
Local file inclusion in ThemeREX Choreo 1.6 and earlier allows remote attackers to include local files without authentication. The public record does not identify the affected file, function, request parameter, or included-file constraint, so exact read or execution outcomes remain undisclosed.
The record
- CVE
- CVE-2025-69165
- Published
- Jun 16, 2026
- Updated
- Jun 16, 2026
- Vendor
- ThemeREX
- Product
- Choreo
- Classifications
- CWE-98, CAPEC-252, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2026CVE publishedPublication date reported by the CVE source.
- Jun 16, 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=n/a <=1.6
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