# CVE-2024-44902: ThinkPHP deserialization vulnerability

> Attackers can execute arbitrary code via a deserialization flaw in the ThinkPHP framework, requiring immediate upgrades.

- **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:** 9 Sep 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-f4wh-359g-4pq7

## What is CVE-2024-44902?

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

### Official description

A deserialization vulnerability in Thinkphp v6.1.3 to v8.0.4 allows attackers to execute arbitrary code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-44902?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `topthink/framework` | Packagist | From 6.1.3 to 8.0.4 | None |
| `topthink/framework` | Packagist | From 6.1.3 to 8.0.4 | None |

Products: Thinkphp Thinkphp.

## How do I fix CVE-2024-44902?

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

## Is CVE-2024-44902 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44902 exists.

Public exploit code:

- https://github.com/fru1ts/CVE-2024-44902 (github_poc): https://github.com/fru1ts/CVE-2024-44902
- Vulnerable ThinkPHP 8.0.4 test environment for CVE-2024-44902 nuclei template validation (github_poc): https://github.com/KrE80r/CVE-2024-44902-env

## 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-2022-45982](https://insights.sbomify.com/CVE-2022-45982/): Deserialization of Untrusted Data in thinkphp (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44902 and fix it if it is affected.

What it is: CVE-2024-44902 is a critical unsafe deserialization vulnerability in n/a, published on 9 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44902 exists.

Affected packages and fixed versions:
- topthink/framework (Packagist): affected from 6.1.3 up to 8.0.4; no fix listed
- topthink/framework (Packagist): affected from 6.1.3 up to 8.0.4; 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-2024-44902/ (Markdown: https://insights.sbomify.com/CVE-2024-44902/index.md)
```

## Sources

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

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