CVE-2025-30081 is a medium-severity (CVSS 6.3) vulnerability in clickstorm/cs-seo. A fix is available for clickstorm/cs-seo — see the affected versions and patch details below.
Clickstorm SEO Allows Cross-Site Scripting (XSS)
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
A cross-site scripting (XSS) vulnerability has been discovered in the Clickstorm SEO extension. This vulnerabily is exploitable by a logged in backend user utilizing the TYPO3 backend user interface. This user can create output in the HTML context by exploiting improperly encoded user input. Updates 6.7.0, 7.4.0, 8.3.0 and 9.2.0 are available for download.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | clickstorm/cs-seo | ≥ 9.0.0&&< 9.2.0 | 9.2.0composer require clickstorm/cs-seo:^9.2.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 8.0.0&&< 8.3.0 | 8.3.0composer require clickstorm/cs-seo:^8.3.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 7.0.0&&< 7.4.0 | 7.4.0composer require clickstorm/cs-seo:^7.4.0 |
| 🐘Packagist | clickstorm/cs-seo | ≥ 6.0.0&&< 6.7.0 | 6.7.0composer require clickstorm/cs-seo:^6.7.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.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-30081 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-30081 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-30081. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-30081 in your dependencies?
O3 Security finds CVE-2025-30081 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.