YesWiki has Multiple Reflected Cross-site Scripting Vulnerabilities

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 Unauthenticated Reflected XSS In this one, most of the parameters can be used to deliver an XSS payload, not just the template parameter. Impact The reflected XSS vulnerabilities identified pose a significant risk to both application integrity and user safety. When combined with other issues discovered…

Published by the source

1 Apr 2026, 00:24 UTC

Last modified by the source

1 Apr 2026, 00:24 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5724-x3rh-5qqq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5724-x3rh-5qqq

Advisory: YesWiki has Multiple Reflected Cross-site Scripting Vulnerabilities
IDs: GHSA-5724-x3rh-5qqq
Record: https://patchnext.com/advisories/ghsa-5724-x3rh-5qqq (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: yeswiki/yeswiki 4.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist yeswiki/yeswiki: affected < 4.6.0; fixed in 4.6.0

## Suggested inspection (read-only)
- Packagist yeswiki/yeswiki: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on yeswiki/yeswiki.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5724-x3rh-5qqq (GitHub-reviewed advisory GHSA-5724-x3rh-5qqq lists affected ranges: Packagist yeswiki/yeswiki >=0 <4.6.0)

Commands are suggestions: review each one before running it.