CVE-2025-48203 is a medium-severity (CVSS 5.5) Cross-site Scripting (XSS) vulnerability in clickstorm/cs-seo. A fix is available for clickstorm/cs-seo — see the affected versions and patch details below.
[clickstorm] SEO (cs_seo) TYPO3 extension Cross-site Scripting (XSS) vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48203.
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
clickstorm/cs-seo🐘clickstorm/cs-seo🐘clickstorm/cs-seo🐘clickstorm/cs-seoReal-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
Cross-site scripting (XSS) vulnerability in the [clickstorm] SEO (cs_seo) TYPO3 extension allows backend users to execute arbitrary script via the JSON-LD output.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | clickstorm/cs-seo | ≥ 9.0.0&&< 9.3.0 | 9.3.0composer require clickstorm/cs-seo:^9.3.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 8.0.0&&< 8.4.0 | 8.4.0composer require clickstorm/cs-seo:^8.4.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 7.0.0&&< 7.5.0 | 7.5.0composer require clickstorm/cs-seo:^7.5.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 6.3.0&&< 6.8.0 | 6.8.0composer require clickstorm/cs-seo:^6.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clickstorm/cs-seo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update clickstorm/cs-seo to 9.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48203 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 CVE-2025-48203 in your dependencies?
Find it across Packagist, including transitive dependencies.