cve.bz

CVE-2022-38352 thinkphp thinkphp: Deserialization of Untrusted Data

9.8 criticalExploit referenceEPSS 22%

Critical (9.8) in thinkphp thinkphp. EPSS 22% estimated probability of exploitation activity in the next 30 days.

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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
22% (unchanged from 22% a week ago; 21% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2022-38352 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-38352?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-38352?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-38352 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
thinkphp:thinkphp6.0.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qjjj-7g7h-54v3Packagisttopthink/framework<=6.0.13no fix published

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON