How severe is GHSA-j543-vg33-g6vj?

GHSA-j543-vg33-g6vj has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-j543-vg33-g6vj?

GHSA-j543-vg33-g6vj affects the following packages: zendframework/zendframework1 (Packagist), zendframework/zendframework1 (Packagist), zendframework/zendframework1 (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j543-vg33-g6vj?

Update zendframework/zendframework1 to 1.7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j543-vg33-g6vj is resolved across your whole dependency graph.

How do I detect GHSA-j543-vg33-g6vj in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j543-vg33-g6vj if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-j543-vg33-g6vj?

O3 pinpoints whether GHSA-j543-vg33-g6vj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j543-vg33-g6vj actively exploited in the wild?

No public exploit code has been indexed for GHSA-j543-vg33-g6vj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-j543-vg33-g6vj published, and has it been updated?

GHSA-j543-vg33-g6vj was published on June 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-j543-vg33-g6vj

MEDIUM

ZendFramework potential Cross-site Scripting vector in `Zend_Dojo_View_Helper_Editor`

Published

Jun 7, 2024

Updated

Jun 7, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐘zendframework/zendframework1🐘zendframework/zendframework1🐘zendframework/zendframework1

Real-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_Dojo_View_Helper_Editor was incorrectly decorating a TEXTAREA instead of a DIV. The Dojo team has reported that this has security implications as the rich text editor they use is unable to escape content for a TEXTAREA.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zendframework/zendframework1`	≥ 1.7.0&&< 1.7.9	1.7.9
🐘Packagist	`zendframework/zendframework1`	≥ 1.8.0&&< 1.8.5	1.8.5
🐘Packagist	`zendframework/zendframework1`	≥ 1.9.0&&< 1.9.7	1.9.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-j543-vg33-g6vj 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 pinpoints whether GHSA-j543-vg33-g6vj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j543-vg33-g6vj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`Zend_Dojo_View_Helper_Editor` was incorrectly decorating a TEXTAREA instead of a DIV. The Dojo team has reported that this has security implications as the rich text editor they use is unable to escape content for a TEXTAREA.

O3 Security · Impact-Aware SCA

Is GHSA-j543-vg33-g6vj in your dependencies?

O3 detects GHSA-j543-vg33-g6vj across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works