# CVE-2022-38352: ThinkPHP deserialization vulnerability

> Attackers can execute arbitrary code in ThinkPHP via a deserialization vulnerability in the Flysystem cache component.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qjjj-7g7h-54v3

## What is CVE-2022-38352?

CVE-2022-38352 is a critical unsafe deserialization vulnerability in n/a, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ThinkPHP v6.0.13 was discovered to contain a deserialization vulnerability via the component League\Flysystem\Cached\Storage\Psr6Cache. This vulnerability allows attackers to execute arbitrary code via a crafted payload.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-38352?

2 open source packages ship an affected version, including topthink/framework. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `topthink/framework` | Packagist | All versions to 6.0.13 | None |
| `topthink/framework` | Packagist | All versions to 6.0.13 | None |

Products: Thinkphp Thinkphp.

## How do I fix CVE-2022-38352?

No fix has been published for CVE-2022-38352 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-38352 being exploited?

There is no known exploitation of CVE-2022-38352 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-63888](https://insights.sbomify.com/CVE-2025-63888/): Code injection in n/a (critical 9.8)
- [CVE-2025-50706](https://insights.sbomify.com/CVE-2025-50706/): ThinkPHP Path Traversal Vulnerability (critical 9.8)
- [CVE-2025-50707](https://insights.sbomify.com/CVE-2025-50707/): Code injection in n/a (critical 9.8)
- [CVE-2024-48112](https://insights.sbomify.com/CVE-2024-48112/): ThinkPHP deserialization vulnerability (critical 9.8)
- [CVE-2024-44902](https://insights.sbomify.com/CVE-2024-44902/): ThinkPHP deserialization vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38352 and fix it if it is affected.

What it is: CVE-2022-38352 is a critical unsafe deserialization vulnerability in n/a, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38352 in the wild and no public exploit code.

Affected packages and fixed versions:
- topthink/framework (Packagist): affected all versions up to 6.0.13; no fix listed
- topthink/framework (Packagist): affected all versions up to 6.0.13; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-38352/ (Markdown: https://insights.sbomify.com/CVE-2022-38352/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-38352
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-38352
- OSV: https://osv.dev/vulnerability/CVE-2022-38352

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-38352/
Summaries are generated and may contain mistakes; the official description above is the record.