CVE-2024-1117
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was found in openBI up to 1.0.8. It has been declared as critical. Affected by this vulnerability is the function index of the file /application/index/controller/Screen.php. The manipulation of the argument fileurl leads to code injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-252475.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical code injection vulnerability exists in openBI up to version 1.0.8 in the /application/index/controller/Screen.php file's index function. The fileurl parameter is not properly sanitized, allowing remote attackers to inject and execute arbitrary code on the server. The exploit is publicly disclosed and actively exploitable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify openBI versionLocate the version file in the openBI installation directory, typically in a version.php, composer.json, or check the admin dashboard for version informationAffected if Installed version is 1.0.8 or lower
-
Verify vulnerable file existsCheck if the file /application/index/controller/Screen.php exists in the web root directoryAffected if The file Screen.php exists in the application directory
-
Confirm web-accessible application directoryVerify that the /application directory is accessible via the web server (not blocked by .htaccess or web server configuration)Affected if The application directory is web-accessible and the Screen.php controller can be reached via HTTP requests
-
Inspect the index function for unsanitized parameterExamine the index function in Screen.php and locate the fileurl parameter handling to verify if user input is used without proper sanitizationAffected if The fileurl parameter is processed without sanitization and allows arbitrary input to be passed to sensitive functions
A system is affected if it runs openBI version 1.0.8 or lower, has the Screen.php file accessible via web, and uses the vulnerable fileurl parameter without input validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and sanitization on the fileurl parameter, preferably using allowlist validation. If available, upgrade to a patched version. Consider applying web application firewall rules as a temporary mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1117 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data