CVE-2024-1116
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 classified as critical. Affected is the function index of the file /application/plugins/controller/Upload.php. The manipulation leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-252474 is the identifier assigned to this vulnerability.
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 confidenceopenBI up to version 1.0.8 contains an unrestricted file upload vulnerability in the /application/plugins/controller/Upload.php file's index function. Attackers can remotely upload arbitrary files (likely PHP scripts) due to insufficient validation of file types, extensions, and content during the upload process. The public disclosure of working exploits increases the likelihood of active exploitation.
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 installation and versionLocate the openBI installation directory and check version files (such as version.php, composer.json, or a README file) to determine the installed version number.Affected if The installed version is 1.0.8 or lower.
-
Locate vulnerable upload scriptSearch for the file /application/plugins/controller/Upload.php in the web application's directory structure.Affected if The file exists in the expected path, indicating the vulnerable component is present.
-
Verify upload endpoint accessibilityCheck if the upload functionality is accessible via HTTP by attempting to access the /application/plugins/controller/Upload.php endpoint or reviewing web server access logs for requests to this endpoint.Affected if The upload script is accessible over the network and responds to requests.
-
Inspect file validation in Upload.phpOpen the Upload.php file and examine the index function to determine if file extension, MIME type, and content (magic bytes) validation is implemented.Affected if The code lacks proper validation of file extensions, MIME types, or file content before saving uploaded files.
You are affected if openBI version 1.0.8 or lower is installed and the /application/plugins/controller/Upload.php file exists with insufficient file validation logic.
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 dataImmediately restrict or disable the file upload functionality until proper validation can be implemented: validate file extensions/MIME types against allowlists, verify file content (magic bytes), store uploads outside the webroot in non-executable directories, and apply principle of least privilege to upload handlers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1116 — 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-1116 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