Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105124 Overview
CVE-2026-105124 is a stored cross-site scripting (XSS) vulnerability in W (vincent-peugnet/wcms) through version 3.18.0. The flaw allows unauthenticated attackers to inject script payloads through two separate input vectors: the login username field and the visitor comment website field. Failed login attempts are written to the admin log and later rendered without output encoding in adminlog.php. Comment URLs are echoed directly into href attributes in editrightbar.php. When administrators or editors view the affected pages, injected scripts execute in their browser context under privileged sessions.
Critical Impact
Unauthenticated attackers can execute arbitrary JavaScript in the browser sessions of administrators and editors, enabling account takeover of privileged WCMS users.
Affected Products
- W (vincent-peugnet/wcms) through version 3.18.0
- app/view/templates/adminlog.php log viewer component
- app/view/templates/editrightbar.php comment rendering component
Discovery Timeline
- 2026-10-04 - CVE-2026-105124 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-105124
Vulnerability Analysis
The vulnerability is a stored XSS flaw categorized under [CWE-79]. WCMS captures attacker-controlled strings from two unauthenticated input surfaces and later outputs them into HTML contexts without applying contextual escaping. The first sink is the administrator log viewer, which displays prior failed login attempts. The second sink is the editor sidebar, which renders visitor-submitted comment metadata. Because both sinks render in authenticated administrator or editor sessions, successful exploitation runs script with elevated privileges inside the WCMS admin interface.
Root Cause
The underlying defect is missing output encoding on user-controlled data persisted to storage and later reflected in HTML. In Controllerconnect.php, failed login attempts record the submitted username verbatim. The adminlog.php template subsequently renders those entries without HTML entity encoding. Separately, editrightbar.php interpolates comment website URLs directly into an href attribute without URL validation or attribute-context escaping.
Attack Vector
An unauthenticated attacker submits a crafted username containing an HTML or script payload to the login form. The payload is stored in the admin log. When an administrator opens the log viewer, the payload executes in the administrator session. Alternatively, an attacker submits a comment with a website URL containing a javascript: scheme or attribute-breaking payload. When an editor loads the page where the comment is referenced, the payload executes in the editor context. User interaction by a privileged victim is required, but no authentication is required from the attacker.
Technical details are documented in the VulnCheck Advisory on WCMS XSS and the upstream GitHub Issue #662.
Detection Methods for CVE-2026-105124
Indicators of Compromise
- Entries in the WCMS admin log containing HTML tags, <script> markers, or event handler attributes such as onerror= or onload= within the username field.
- Stored comment records where the website URL begins with javascript: or contains quote characters that break out of the href attribute.
- Unexpected outbound requests from administrator or editor browsers to attacker-controlled domains shortly after viewing the admin log or edit sidebar.
Detection Strategies
- Review database and file-based storage of failed login records for payloads containing angle brackets or scheme prefixes.
- Inspect HTTP POST bodies to the login and comment endpoints for payloads that contain script fragments or attribute-breaking characters.
- Hunt administrator session activity for anomalous API calls, content changes, or privilege modifications following access to adminlog.php or editrightbar.php.
Monitoring Recommendations
- Deploy a web application firewall rule that flags login usernames and comment website fields containing <, >, or javascript:.
- Enable Content Security Policy (CSP) reporting to surface inline script execution and blocked script loads inside the WCMS admin UI.
- Alert on administrator and editor accounts generating outbound requests to previously unseen domains during admin console use.
How to Mitigate CVE-2026-105124
Immediate Actions Required
- Restrict access to the WCMS login and comment endpoints to known IP ranges or behind an authenticating reverse proxy where feasible.
- Clear existing admin log entries and stored comment records after reviewing them for injected payloads.
- Instruct administrators and editors to avoid loading adminlog.php and comment-managing views until the application is patched or hardened.
Patch Information
At the time of publication, no fixed release later than 3.18.0 is referenced in the NVD entry. Monitor the upstream GitHub WCMS Repository and GitHub Issue #662 for a patched version. Review the vulnerable sinks at Controllerconnect.php line 56, adminlog.php line 71, and editrightbar.php line 110 to apply local fixes.
Workarounds
- Apply a local patch that wraps rendered log usernames with htmlspecialchars($value, ENT_QUOTES, 'UTF-8') in adminlog.php.
- Validate comment website URLs server-side to reject non-http(s) schemes and escape attribute output in editrightbar.php.
- Deploy a strict Content Security Policy on the WCMS admin interface that disallows inline scripts and restricts script sources to trusted origins.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

