CVE-2026-104473 YesWiki CVE debrief

Who should care

Defenders of YesWiki installations, especially those with unauthenticated or public-facing access, should assess exposure and prioritize remediation due to the potential for session hijacking and unauthorized actions.

Why it matters

CVE-2026-104473 is a reflected XSS vulnerability in YesWiki before 4.5.3, allowing remote attackers to inject JavaScript. Defenders should prioritize remediation due to potential session hijacking and unauthorized actions.

• Session hijacking through crafted links
• Potential for authenticated requests against backend functionality
• Need for input validation and sanitization

Technical summary

The vulnerability exists in YesWiki before version 4.5.3, allowing remote attackers to inject JavaScript through unsanitized parameters such as incomingurl, id, file, tags, and template. This could lead to session hijacking and authenticated requests against backend functionality. The vulnerability is a result of inadequate input validation and sanitization of user-supplied data. Attackers can lure authenticated or unauthenticated users into opening crafted links to hijack sessions and trigger authenticated requests against backend functionality. The vulnerability has a CVSS score of 5.1 and a severity rating of MEDIUM. Defenders should prioritize remediation due to the potential for session hijacking and

Defensive priority

Medium priority for defenders of YesWiki installations, especially those with unauthenticated or public-facing access.

Recommended defensive actions

• Upgrade to version 4.5.3 or later
• Implement input validation and sanitization for user-supplied parameters
• Monitor for suspicious activity and implement session management best practices
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including affected versions and potential attack vectors. However, there is limited information on actual exploitation or victim impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.