How severe is GHSA-5724-x3rh-5qqq?

No CVSS score has been assigned to GHSA-5724-x3rh-5qqq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5724-x3rh-5qqq?

GHSA-5724-x3rh-5qqq affects the following packages: yeswiki/yeswiki (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5724-x3rh-5qqq?

Update yeswiki/yeswiki to 4.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5724-x3rh-5qqq is resolved across your whole dependency graph.

How do I detect GHSA-5724-x3rh-5qqq in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yeswiki/yeswiki. 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-5724-x3rh-5qqq 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-5724-x3rh-5qqq?

O3 pinpoints whether GHSA-5724-x3rh-5qqq 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-5724-x3rh-5qqq actively exploited in the wild?

No public exploit code has been indexed for GHSA-5724-x3rh-5qqq 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-5724-x3rh-5qqq published, and has it been updated?

GHSA-5724-x3rh-5qqq was published on April 1, 2026 and was last updated on April 1, 2026. 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-5724-x3rh-5qqq

YesWiki has Multiple Reflected Cross-site Scripting Vulnerabilities

Published

Apr 1, 2026

Updated

Apr 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘yeswiki/yeswiki

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

Summary

Multiple reflected Cross-site Scripting (XSS) vulnerabilities across both authenticated and unauthenticated portions of the application. These findings present a significant security risk, as they can be leveraged to execute arbitrary JavaScript in a victim’s browser under various contexts.

Impact and Exploitation

While XSS is often treated as a standalone issue, these vulnerabilities have broader implications. Specifically, they can be used as launch points to exploit other significant vulnerabilities.

Proof of concept links follow. All testing was performed on my local docker setup running the lastest version of the application.

Proof of Concepts

Authenticated Reflected XSS

http://localhost:8085/?ElizabethJFeinler/deletepage&incomingurl=%22%3E%3Cscript%3Ealert(1)%3C%2fscript%3E

http://localhost:8085/?BazaR&vue=saisir&action=saisir_fiche&id=%3Cscript%3Ealert(1)%3C%2fscript%3E

http://localhost:8085/?GererThemes/upload&file=%3Cscript%3Ealert(1)%3C/script%3E

Unauthenticated Reflected XSS

http://localhost:8085/?PagePrincipale/listpages&tags=%22%3E%3Cscript%3Ealert(1)%3C/script%3E

In this one, most of the parameters can be used to deliver an XSS payload, not just the template parameter.

http://localhost:8085/?BazaR/bazariframe&id=2&template=<script>alert(1)</script>&width=100%25&height=600px&lat=46.22763&lon=2.213749&markersize=big&provider=MapBox&zoom=5&groups=&titles=&groupsexpanded=false

Impact

The reflected XSS vulnerabilities identified pose a significant risk to both application integrity and user safety. When combined with other issues discovered such as insecure endpoints or improper authentication mechanisms. These XSS flaws can be leveraged to escalate access, hijack sessions, and in some cases, achieve remote code execution (RCE). For example, malicious JavaScript executed via XSS could be used to trigger authenticated requests that exploit backend vulnerabilities, ultimately allowing an attacker to execute arbitrary commands on the server or pivot deeper into the environment.

Mitigation

Update to version 4.6.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`yeswiki/yeswiki`	all versions	4.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yeswiki/yeswiki. 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 yeswiki/yeswiki to 4.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5724-x3rh-5qqq 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-5724-x3rh-5qqq 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-5724-x3rh-5qqq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Multiple **reflected Cross-site Scripting (XSS)** vulnerabilities across both **authenticated and unauthenticated** portions of the application. These findings present a significant security risk, as they can be leveraged to execute arbitrary JavaScript in a victim’s browser under various contexts. ## Impact and Exploitation While XSS is often treated as a standalone issue, these vulnerabilities have broader implications. Specifically, they can be used as **launch points to exploit other significant vulnerabilities**. Proof of concept links follow. All testing was performed on

O3 Security · Impact-Aware SCA

Is GHSA-5724-x3rh-5qqq in your dependencies?

O3 detects GHSA-5724-x3rh-5qqq 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