GHSA-5724-X3RH-5QQQ

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

Mitigation

Update to version 4.6.0

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Kodem intelligence

1. What is GHSA-5724-X3RH-5QQQ? GHSA-5724-X3RH-5QQQ is a medium-severity cross-site scripting (XSS) vulnerability in yeswiki/yeswiki (composer), affecting versions < 4.6.0. It is fixed in 4.6.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. Which versions of yeswiki/yeswiki are affected by GHSA-5724-X3RH-5QQQ? yeswiki/yeswiki (composer) versions < 4.6.0 is affected.
3. Is there a fix for GHSA-5724-X3RH-5QQQ? Yes. GHSA-5724-X3RH-5QQQ is fixed in 4.6.0. Upgrade to this version or later.
4. Is GHSA-5724-X3RH-5QQQ exploitable, and should I be worried? Whether GHSA-5724-X3RH-5QQQ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-5724-X3RH-5QQQ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-5724-X3RH-5QQQ? Upgrade yeswiki/yeswiki to 4.6.0 or later.