GHSA-4vf6-mq7w-3hp6 — zendframework/zendframewo…
MEDIUMGHSA-4vf6-mq7w-3hp6 is a medium-severity (CVSS 6.1) vulnerability in zendframework/zendframework1. A fix is available for zendframework/zendframework1 — see the affected versions and patch details below.
Zend_Filter_StripTags vulnerable to Cross-site Scripting when comments allowed
Real-World Exposure
zendframework/zendframework1🐘zendframework/zendframework1🐘zendframework/zendframework1Real-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
Zend_Filter_StripTags contained an optional setting to allow whitelisting HTML comments in filtered text. Microsoft Internet Explorer and several other browsers allow developers to create conditional functionality via HTML comments, including execution of script events and rendering of additional commented markup. By allowing whitelisting of HTML comments, a malicious user could potentially include XSS exploits within HTML comments that would then be rendered in the final output.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | zendframework/zendframework1 | ≥ 1.7.0&&< 1.7.9 | 1.7.9composer require zendframework/zendframework1:^1.7.9 |
| 🐘Packagist | zendframework/zendframework1 | ≥ 1.8.0&&< 1.8.5 | 1.8.5composer require zendframework/zendframework1:^1.8.5 |
| 🐘Packagist | zendframework/zendframework1 | ≥ 1.9.0&&< 1.9.7 | 1.9.7composer require zendframework/zendframework1:^1.9.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zendframework/zendframework1 to 1.7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4vf6-mq7w-3hp6 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 GHSA-4vf6-mq7w-3hp6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4vf6-mq7w-3hp6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4vf6-mq7w-3hp6 in your dependencies?
O3 Security finds GHSA-4vf6-mq7w-3hp6 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.