CVE-2019-12901
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 · uneditedPydio Cells before 1.5.0 fails to neutralize '../' elements, allowing an attacker with minimum privilege to Upload files to, and Delete files/folders from, an unprivileged directory, leading to Privilege escalation.
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 confidencePydio Cells before version 1.5.0 contains a path traversal vulnerability where the application fails to properly sanitize or neutralize '../' sequences in user-controlled file paths. An attacker with minimal privileges can manipulate file upload and deletion operations to write files to or delete files from directories outside the intended scope, enabling privilege escalation.
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.5.0CVSS 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.
-
Determine Pydio Cells installed versionRun the command 'cells --version' or check the application admin dashboard under 'About' or 'System Information' sections to find the exact version numberAffected if The displayed version is below 1.5.0 (for example, 1.4.x, 1.3.x, etc.)
-
Verify if file upload functionality is enabledCheck the application configuration files (typically in /opt/pydio/cells or the installation directory) for 'enableUpload' or 'enableWebDAV' settings, or inspect the Roles and Policies in the admin interface to see if standard users have file creation permissionsAffected if File upload or file creation capabilities are available to authenticated users
-
Confirm user access to file path parametersInspect the API endpoints or UI forms that accept file paths for upload, move, copy, or delete operations. Look for parameters that accept user-supplied path strings rather than selecting from a pre-defined treeAffected if The application accepts custom file path strings from users for file operations
-
Check for path traversal protection in logsReview application logs (typically in /var/log/pydio/cells.log or similar) for recent path traversal attempts, failed file operations with '../' patterns, or security events related to file access violationsAffected if Logs show successful or attempted traversal with '../' sequences in file paths
A user is affected if their installed Pydio Cells version is below 1.5.0 and the file upload or file management features are accessible to authenticated users, allowing them to supply custom file paths.
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 data1.5.0
Upgrade Pydio Cells to version 1.5.0 or later. As an immediate workaround, implement strict input validation to reject path arguments containing '../' sequences and enforce path containment checks before file operations.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12901 — 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-2019-12901 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