Unauthenticated code injection via fileurl parameter
Published Jan 31, 2024 · Updated May 29, 2025
Code injection in openBI 1.0.8 and earlier allows remote attackers to inject code through the fileurl parameter. The published record identifies the index function in /application/index/controller/Screen.php but does not disclose the code path or sink that evaluates the input. No authentication or user interaction is required, but public evidence does not establish execution beyond the openBI application context.
Summary
What happened
Code injection in openBI 1.0.8 and earlier allows remote attackers to inject code through the fileurl parameter. The published record identifies the index function in /application/index/controller/Screen.php but does not disclose the code path or sink that evaluates the input. No authentication or user interaction is required, but public evidence does not establish execution beyond the openBI application context.
The record
- CVE
- CVE-2024-1117
- Published
- Jan 31, 2024
- Updated
- May 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 31, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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