Vulnerability record · CVE-2018-20718 · published 15 January 2019
CVE-2018-20718: Pydio deserialization of untrusted data vulnerability
Pydio · Pydio
In Pydio before 8.2.2, an attack is possible via PHP Object Injection because a user is allowed to use the $phpserial$a:0:{} syntax to store a preference. An attacker either needs a "public link" of a file, or access to any unprivileged user account for creation of such a link.
Description
In Pydio before 8.2.2, an attack is possible via PHP Object Injection because a user is allowed to use the $phpserial$a:0:{} syntax to store a preference. An attacker either needs a "public link" of a file, or access to any unprivileged user account for creation of such a link.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://blog.ripstech.com/2018/pydio-unauthenticated-remote-code-execution/ | ExploitThird Party Advisory |
| https://blog.ripstech.com/2018/pydio-unauthenticated-remote-code-execution/ | ExploitThird Party Advisory |
Track CVE-2018-20718 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2018-20718), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.