CVE-2018-25412
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 · uneditedDelta Sql 1.8.2 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by sending POST requests to docs_upload.php with crafted multipart form data. Attackers can upload PHP files with arbitrary content to the upload directory and execute them on the server for remote code execution.
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 confidenceDelta Sql 1.8.2 has an unauthenticated arbitrary file upload vulnerability in docs_upload.php. Attackers can send crafted multipart form data via POST requests to upload malicious PHP files to the server, achieving 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.8.2CVSS 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 DeltaSQL versionLocate and inspect the version file or check the login/main page for the version string. Common paths include version.php, about.php, or displayed in the footer of the web interface.Affected if The installed version is exactly 1.8.2
-
Locate docs_upload.phpSearch the web application directory for the file docs_upload.php. This file is typically found in the /docs/ or /upload/ subdirectory of the webroot.Affected if The file docs_upload.php exists in the application directory
-
Verify upload endpoint accessibilityAttempt to access docs_upload.php directly via HTTP/HTTPS without providing any credentials. For example: GET /docs_upload.php or /path/to/docs_upload.phpAffected if The upload script is accessible without authentication (no login prompt or 401/403 error)
-
Inspect upload directory configurationCheck the web server configuration and the upload script to determine where uploaded files are stored. Verify if the upload directory is within the webroot and if script execution is allowed.Affected if Uploaded files are stored inside the webroot and the directory allows PHP script execution
-
Check file validation in upload scriptOpen docs_upload.php and inspect the code for file type validation. Look for checks on file extensions, MIME types, or content-type headers before moving uploaded files.Affected if The upload script lacks proper file type validation or allows .php file extensions
A user is affected if they are running DeltaSQL version 1.8.2 with the docs_upload.php file accessible without authentication and with uploaded files stored in a location that permits script execution.
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 authentication/authorization checks on docs_upload.php, validate file types using magic bytes not just extensions, rename uploaded files, and store uploads outside the web root or with non-executable extensions.
- 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-2018-25412 — 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-2018-25412 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