CVE-2024-1034
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, which was classified as critical, was found in openBI up to 1.0.8. This affects the function uploadFile of the file /application/index/controller/File.php. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-252309 was 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 confidenceUnrestricted file upload vulnerability in openBI up to version 1.0.8. The uploadFile function in /application/index/controller/File.php accepts files without proper validation, allowing attackers to upload arbitrary files (including executable scripts) to the server. This can lead to remote code execution.
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 versionCheck the version file or composer.json in the webroot for the installed openBI version. Common locations include /application/version.php, /VERSION file, or the admin panel 'About' page.Affected if The installed version is 1.0.8 or lower, or if no version can be determined and the application is known to be openBI.
-
Verify vulnerable file existsCheck if the file /application/index/controller/File.php exists in the webroot. This is the file containing the vulnerable uploadFile function.Affected if The file /application/index/controller/File.php exists and is accessible within the web directory structure.
-
Confirm upload functionality is exposedTest for the presence of the file upload endpoint by checking if /index.php/file/uploadFile or similar routes are accessible via HTTP. Review routing configuration in /application/route.php or the web server logs for upload-related requests.Affected if The upload endpoint is reachable and responds to requests (HTTP 200 or 403 rather than 404).
-
Check for executable file permissions in uploads directoryExamine the upload directory configuration in File.php or the application settings. Identify the upload path (commonly /uploads/ or /public/uploads/) and verify if .php, .exe, or other script extensions can be executed from that directory.Affected if The configured upload directory allows execution of uploaded files (no .htaccess restrictions, no DisableExecutes in web server config for that path).
-
Search for suspicious uploaded filesSearch the uploads directory for unexpected file extensions (.php, .phtml, .php5, .asp, .jsp, .exe, .sh). Check file modification timestamps for recent unexpected uploads. Review web server access logs for suspicious POST requests to upload endpoints.Affected if Executable scripts or suspicious files are found in the upload directory that were not intentionally placed there by administrators.
A system is affected if it runs openBI version 1.0.8 or lower AND the File.php upload functionality is accessible and allows executable file types in the upload directory.
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 file type validation (allowlist approach), validate file content/magic bytes, rename uploaded files, store uploads outside webroot, and disable script execution in the upload directory.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1034 — 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-1034 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