CVE-2018-19114
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 · uneditedAn issue was discovered in MinDoc through v1.0.2. It allows attackers to gain privileges by uploading an image file with contents that represent an admin session, and then sending a Cookie: header with a mindoc_id value containing the relative pathname of this uploaded file. For example, the mindoc_id (aka session ID) could be of the form aa/../../uploads/blog/201811/attach_#.jpg where '#' is a hex value displayed in the upload field of a manage/blogs/edit/ screen.
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 · moderate confidenceMinDoc through v1.0.2 allows privilege escalation via a path traversal vulnerability in session handling. Attackers upload a file (disguised as an image) containing admin session data, then exploit the mindoc_id cookie parameter to traverse paths (e.g., aa/../../uploads/blog/201811/attach_#.jpg) and reference this file, causing the application to use the uploaded content as a valid admin session.
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.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check MinDoc versionLocate the MinDoc installation directory and find the version file or binary. Typical locations include the root directory of the web application. Look for a version file, about page, or check the binary/version string.Affected if Installed version is 1.0.2 or any version through v1.0.2 (versions greater than 1.0.2 are not affected)
-
Verify file upload functionality is enabledCheck if the uploads directory (typically /uploads/blog/ or similar under the web root) exists and is writable by the application. Test if file upload feature is accessible to non-admin users.Affected if Uploads directory exists and accepts file uploads from users (this is required for the attack vector)
-
Inspect session handling configurationExamine the application configuration files for session storage settings. Look for any configuration that allows session data to be referenced via file paths rather than server-side session stores.Affected if Sessions are stored or referenced via file paths that can be influenced by user input (the mindoc_id cookie parameter)
-
Test mindoc_id cookie for path traversalSend HTTP requests with manipulated mindoc_id cookie values containing path traversal sequences (such as aa/../../uploads/blog/201811/attach_#.jpg) and observe if the application attempts to load files from arbitrary paths.Affected if The application accepts and processes path traversal sequences in the mindoc_id cookie parameter and uses the resulting path to load session data
A user is affected if MinDoc version is 1.0.2 or earlier AND the application accepts file uploads AND the mindoc_id cookie parameter can be manipulated to traverse paths and reference uploaded files as session data.
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 dataUpgrade to a patched version of MinDoc beyond v1.0.2. Additionally, implement strict input validation on the mindoc_id cookie parameter to prevent path traversal and store session data server-side rather than accepting file-path references.
- Consultation4.0 h
- Implementation12.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19114 — 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-19114 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