CVE-2019-12902
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 does incomplete cleanup of a user's data upon deletion. This allows a new user, holding the same User ID as a deleted user, to restore the deleted user's data.
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 confidenceIn Pydio Cells before version 1.5.0, user data is not fully cleaned up when a user account is deleted. If a new user account is created with the same User ID as a previously deleted user (user ID recycling), that new user can restore or access the deleted user's data, resulting in unauthorized data disclosure and broken data isolation between users.
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed Pydio Cells versionCheck the version of Pydio Cells currently running in your environment. This is typically visible in the admin dashboard under System Information, or can be obtained via the cells version command if you have CLI access.Affected if The installed version is any release prior to version 1.5.0 (for example, 1.4.x, 1.3.x, etc.)
-
Identify user accounts with potential ID reuseReview your user directory to identify any scenarios where a new user account may have been created with a User ID (username or internal identifier) that previously belonged to a deleted account. This can be done by querying the user database or reviewing admin logs for user deletion and creation events.Affected if A new user exists whose User ID matches that of a previously deleted user, indicating user ID recycling has occurred.
-
Inspect data storage for orphaned user dataExamine the data storage backend (typically the cells-data or personal files directory) for folders or data objects belonging to deleted users that were not removed during the deletion process. Look for user-specific directories that persist after user deletion.Affected if Data directories or files belonging to previously deleted users still exist in the storage system.
-
Verify data isolation between usersLog in as a user who was created with a recycled User ID and attempt to access data. Check if that user can restore, view, or modify data that belonged to the previously deleted user with the same ID.Affected if The user can access data from the previously deleted account, demonstrating broken data isolation.
You are affected if running Pydio Cells version below 1.5.0 AND user ID recycling has occurred, allowing a new user to access a deleted user's 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 data1.5.0
Upgrade to Pydio Cells version 1.5.0 or later, which implements complete data cleanup upon user deletion. For existing deployments, audit for any user ID reuse scenarios and run any provided data cleanup scripts for previously deleted users.
- 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-2019-12902 — 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-12902 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