CVE-2026-105124 vincent-peugnet CVE debrief

Who should care

Defenders responsible for systems using W (vincent-peugnet/wcms) should assess exposure and prioritize verification and remediation efforts. This includes reviewing the current version of the software, implementing input validation and output encoding, and monitoring for suspicious activity. Additionally, defenders should consider the potential operational impacts of this vulnerability, including potential script execution with administrator or editor and

Why it matters

This stored cross-site scripting vulnerability in W (vincent-peugnet/wcms) through 3.18.0 allows unauthenticated attackers to inject scripts, potentially leading to script execution with administrator or editor privileges.

• Potential script execution with administrator or editor privileges.
• Possible unauthorized access to sensitive information.
• Required verification of exposure and impact on systems using the affected software versions.
• Necessity to implement input validation and output encoding to prevent script injection.

Technical summary

The vulnerability exists in W (vincent-peugnet/wcms) through 3.18.0 and allows attackers to inject scripts via the login user field and visitor comment website field. Attackers can submit failed logins rendered unescaped in the adminlog.php log viewer, or comment URLs echoed into href attributes in editrightbar.php, executing script with administrator or editor privileges. Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, particularly those using the affected software versions.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, particularly those using the affected software versions.

Recommended defensive actions

• Verify the version of W (vincent-peugnet/wcms) being used and assess exposure to this vulnerability.
• Implement input validation and output encoding to prevent script injection.
• Monitor for suspicious activity, particularly in the adminlog.php log viewer and editrightbar.php pages.
• 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 vulnerability allows attackers to submit failed logins rendered unescaped in the adminlog.php log viewer, or comment URLs echoed into href attributes in editrightbar.php, executing script with administrator or editor privileges.

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.