CVE-2026-104470 YesWiki CVE debrief

Who should care

YesWiki users and administrators, particularly those with page editing privileges, should assess exposure and prioritize patching to prevent potential exploitation. They should verify the version of YesWiki they are using and check if it is vulnerable. Additionally, they should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

CVE-2026-104470 is a medium-severity server-side request forgery vulnerability in YesWiki before 4.6.7. Page editors can exploit this to make the server fetch arbitrary URLs, potentially reaching internal services and partially reading responses. YesWiki users and administrators should assess exposure, prioritize patching, and monitor for suspicious activity.

• Potential unauthorized access to internal services
• Possible data leakage from partial response rendering
• Need for verification of affected versions and scope
• Priority for patching and monitoring

Technical summary

The vulnerability allows page editors to make the server fetch arbitrary URLs via the url parameter of the Bazar valeur action. Attackers can exploit this by embedding the action with a champ parameter in wiki markup to reach loopback or internal services and partially read responses rendered into the page. This vulnerability affects YesWiki before version 4.6.7 and can be exploited by page editors with sufficient privileges. The vulnerability has a medium severity and requires patching to prevent potential exploitation.

Defensive priority

Medium priority for patching and verification

Recommended defensive actions

• Patch YesWiki to version 4.6.7 or later
• Verify and restrict access to the Bazar valeur action
• Monitor for suspicious activity and potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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

Evidence notes

The CVE record and NVD entry provide details about the vulnerability. However, the exact scope of affected versions and potential impact require further verification from official sources. YesWiki users and administrators should verify the version of YesWiki they are using and check if it is vulnerable. They should also review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. Additionally, defenders should verify the vulnerability's impact on their specific environment and plan vendor-sup,

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.