CVE-2026-105224 YesWiki CVE debrief

Who should care

Defenders responsible for YesWiki installations should assess exposure and prioritize patching or mitigation. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed and review compensating controls for exposed systems while remediation is scheduled and verified. A 7.

Why it matters

CVE-2026-105224 is a cross-site scripting vulnerability in YesWiki before 4.6.7, allowing script injection via unescaped HTML from a remote URL. Defenders should verify exposure, prioritize patching, and monitor for potential script injection attempts.

• Potential script injection in viewer browsers
• Verification of YesWiki installation exposure is required
• Patching or mitigation priority for affected installations

Technical summary

The vulnerability exists in the Bazar valeur action of YesWiki before 4.6.7, allowing page editors to inject script by rendering unescaped HTML fetched from a remote URL. Attackers can exploit this by pointing tools/bazar/actions/valeur.php at a controlled server returning BAZ_fiche_titre markup with an img onerror handler, executing script in every viewer's browser. This vulnerability has a CVSS score of 5.1 and MEDIUM severity. Defenders should prioritize verifying exposure of YesWiki installations to this vulnerability and apply patches or mitigations as available.

Defensive priority

Defenders should prioritize verifying exposure of YesWiki installations to this vulnerability and apply patches or mitigations as available.

Recommended defensive actions

• Verify YesWiki installations for exposure to CVE-2026-105224
• Apply patches or mitigations as available
• Monitor for potential script injection attempts
• 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 NVD entry provide details on the vulnerability, including its CVSS score of 5.1 and MEDIUM severity. However, the corpus does not establish versions beyond 4.6.7, exploitation, impact, or remediation details require verification from official sources.

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.