CVE-2019-20452
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 problem was found in Pydio Core before 8.2.4 and Pydio Enterprise before 8.2.4. A PHP object injection is present in the page plugins/core.access/src/RecycleBinManager.php. An authenticated user with basic privileges can inject objects and achieve 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 confidenceA PHP object injection vulnerability exists in the RecycleBinManager.php file of Pydio Core and Pydio Enterprise before version 8.2.4. The vulnerability allows an authenticated user with basic privileges to inject malicious PHP objects via unsafe deserialization, potentially leading 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< 8.2.4CVSS 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.1/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.
-
Identify installed Pydio versionAccess the Pydio admin dashboard and navigate to Settings > About, or inspect the version.php file in the Pydio installation directory.Affected if The installed version is any release prior to 8.2.4, indicating the vulnerable code is present.
-
Locate RecycleBinManager.php fileSearch the Pydio installation directory for the file RecycleBinManager.php, typically found in the core or plugins directory.Affected if The file exists in the installation and originates from a version before 8.2.4.
-
Verify PHP unserialize function usageInspect the RecycleBinManager.php file for usage of PHP unserialize() on user-controlled input without proper sanitization.Affected if The code contains unsafe unserialize() calls handling input from authenticated users.
-
Confirm basic privilege user accessLog in to Pydio with a standard basic privilege user account and verify access to the Recycle Bin manager functionality.Affected if Basic authenticated users can access features that trigger the vulnerable deserialization code path.
-
Check network accessibilityDetermine if the Pydio application is exposed to untrusted networks or the internet.Affected if The application is reachable from networks where untrusted authenticated users could exploit the vulnerability.
A user is affected if their Pydio installation version is below 8.2.4, the RecycleBinManager.php file with unsafe deserialization is present, and basic authenticated users can reach the vulnerable code path.
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 data8.2.4
Upgrade Pydio Core and Pydio Enterprise to version 8.2.4 or later to resolve the vulnerability. If immediate upgrading is not feasible, restrict network access to the application and monitor for suspicious activity.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20452 — 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-20452 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