ThinkPHP Cross-Site Scripting VulnerabilityGHSA-969f-v7jv-pgj3
MEDIUMFix: top-think/framework@403358cGHSA-969f-v7jv-pgj3 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in topthink/framework. A fix is available for topthink/framework — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-969f-v7jv-pgj3.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
topthink/framework🐘topthink/framework🐘topthink/frameworkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
ThinkPHP 8.0.3 allows remote attackers to exploit XSS due to inadequate filtering of function argument values in think_exception.tpl.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | topthink/framework | ≥ 8.0.0&&< 8.0.4 | 8.0.4composer require topthink/framework:^8.0.4 |
| 🐘Packagist | topthink/framework | ≥ 6.1.0&&< 6.1.5 | 6.1.5composer require topthink/framework:^6.1.5 |
| 🐘Packagist | topthink/framework | all versions | 6.0.17composer require topthink/framework:^6.0.17 |
Affected Products
thinkphpthinkphpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for topthink/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update topthink/framework to 8.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-969f-v7jv-pgj3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-969f-v7jv-pgj3 in your dependencies?
Find it across Packagist, including transitive dependencies.