Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit failed login or comment with scripted username/URL
-
DeliveryPayload stored unescaped in log/comment data
-
ExploitAdmin or editor views adminlog.php or editrightbar.php
-
ExecutionScript executes in privileged browser context
-
ImpactHijack admin/editor session actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Two concrete injection paths exist: (1) an unauthenticated attacker triggers a failed login whose username field is stored and rendered unescaped in the adminlog.php log viewer; (2) a site visitor submits a comment whose website URL is echoed unescaped into an href attribute in editrightbar.php. The critical limiting factor is that payload execution requires a privileged victim (CVSS UI:P) - specifically an administrator viewing the failed-login log, or an administrator/editor viewing the comment panel - so the script runs only in that privileged user's session and only when they visit the affected admin page. No authentication is required of the attacker (PR:N), and default configurations of wcms expose the login and comment inputs, but impact is bounded to the browser context of whichever admin or editor renders the stored data. |
| Impact | This is a stored XSS (CWE-79) in the niche open-source flat-file CMS 'W' (wcms) through 3.18.0, reported by VulnCheck. The only severity signal provided is a CVSS 4.0 score of 5.3 (AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N) - medium severity. The attacker is unauthenticated (PR:N) and the vector is network (AV:N), which raises exposure, but exploitation is gated by passive user interaction (UI:P): a privileged user - an administrator or editor - must view the adminlog.php log viewer or the editrightbar.php comment panel for the injected script to fire. No EPSS score, CISA KEV listing, or public POC is present in the supplied intelligence, so there is no evidence of active exploitation or weaponization. SSVC-style reasoning: exploitation status is 'none' (no public exploit identified), technical impact is partial (low confidentiality/integrity, no availability), and it is not trivially automatable since it depends on a human victim with elevated privileges visiting the rendered page. The input is internally consistent - CVSS 4.0 vector, description, and CWE all agree on a low-impact, interaction-dependent stored XSS - so no signals conflict. Net: a legitimate issue worth patching, but a medium-priority, interaction-gated flaw in a low-footprint product rather than an urgent mass-exploitation threat. Note only a CVSS 4.0 vector was provided; no CVSS 3.1 vector was supplied for direct comparison. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a failed login using a username containing a crafted script payload (or posts a site visitor comment whose website URL carries a javascript/attribute-breaking payload). The payload is stored unescaped and later rendered when an administrator opens the adminlog.php failed-login viewer or an editor views the comment URL in editrightbar.php, executing attacker-controlled script in that privileged user's browser session. No public exploit code was identified at the time of analysis, though the vulnerable sink lines are pinpointed in the referenced GitHub source. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 04, 2026
Stored cross-site scripting in W (wcms) through 3.18.0 lets unauthenticated attackers plant persistent JavaScript that executes in the browser session of an administrator or editor. Two injection paths are present: the username submitted with a failed login is stored and later rendered unescaped in the adminlog.php log viewer, and a visitor-supplied comment website URL is echoed unescaped into an href attribute in editrightbar.php. The payload only fires when a privileged user opens the affected admin page (CVSS 4.0 UI:P; our independent assessment agrees with AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), and no public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
No vendor-released patch version is identified in the available intelligence; the coordination point is the upstream issue https://github.com/vincent-peugnet/wcms/issues/662, with additional detail in the VulnCheck advisory https://www.vulncheck.com/advisories/w-wcms-through-3.18.0-unauthenticated-stored-xss-via-login-username-and-comments, so the primary action is to monitor that issue and upgrade to the first release above 3.18.0 that contains the fix, which should touch the login-username output in app/view/templates/adminlog.php and the comment-URL output in app/view/templates/editrightbar.php. Until an upstream release exists, the most direct control is a local patch that wraps the stored login username in htmlspecialchars with ENT_QUOTES and UTF-8 before output in adminlog.php and does the same for the comment website value in editrightbar.php, and that additionally rejects or normalizes any comment URL whose scheme is not http or https so javascript: and data: URIs cannot be injected into the href attribute; the trade-off is a maintained fork that must be reapplied after each upgrade. Where visitor comments are not essential, disabling the comment feature removes one of the two storage paths outright, at the cost of losing reader interaction, while restricting the admin area behind reverse-proxy authentication, an IP allowlist, or simply making adminlog.php and the comment panel unreachable from untrusted networks prevents the privileged victim from ever rendering a stored payload without fixing the underlying flaw. Because both vectors are persistent, any applied fix must be followed by data cleanup: clear the login-failure log and delete or re-save comments holding suspicious website values, otherwise previously planted payloads remain live. As defense in depth, set the session cookie to HttpOnly and deploy a Content-Security-Policy with script-src 'self' and a nonce, accepting that CSP rules must be validated against the admin UI because inline scripts can break.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-79 (improper neutralization of input during web page generation) in the self-hosted PHP flat-file CMS W, tracked against CPE cpe:2.3:a:vincent-peugnet:wcms:*:*:*:*:*:*:*:* for all releases through 3.18.0. The login controller at app/class/Controllerconnect.php line 56 persists the supplied username on an authentication failure, and app/view/templates/adminlog.php line 71 later emits that stored value into the log-viewer HTML without context-appropriate encoding, so an HTML/script payload survives into the admin page. The second sink is app/view/templates/editrightbar.php line 110, where a comment's website field is written directly into an href attribute; because this is an attribute context, plain HTML entity encoding alone is insufficient and the URL scheme must also be constrained, since a javascript: or data: value would execute on click or render. Both paths require no privileges from the attacker (PR:N) but depend on a privileged victim visiting the affected admin surface (UI:P), which is why the CVSS 4.0 vector records VC:L/VI:L/VA:N with a scope change (SC:L/SI:L) - the script runs with the admin's or editor's browser privileges rather than those of the submitter.
Know when Wcms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Unauthenticated remote injection (PR:N, AV:N) but execution needs a privileged victim to view the page (UI:R); scope changes to the admin/editor browser (S:C) with low confidentiality/integrity impact and no availability loss.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
W (vincent-peugnet/wcms) through 3.18.0 contains a stored cross-site scripting vulnerability that allows unauthenticated 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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
In Wcms 0.3.2, an attacker can send a crafted request from a vulnerable web application backend server /wcms/wex/html.ph
Authenticated users holding editor privileges on wcms through 3.18.0 can turn the media upload API into a remote code ex
wcms/wex/finder/action.php in WCMS v0.3.2 has a Arbitrary File Upload Vulnerability via developer/finder because .php is
A vulnerability has been found in WCMS 11 and classified as critical. Rated medium severity (CVSS 6.9), this vulnerabili
A vulnerability, which was classified as critical, was found in WCMS 11. Rated medium severity (CVSS 6.9), this vulnerab
A vulnerability was found in WCMS 11. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, low
A vulnerability classified as critical was found in vedees wcms up to 0.3.2. Rated medium severity (CVSS 5.3), this vuln
A vulnerability, which was classified as critical, has been found in WCMS 11.php of the component Advertisement Image Ha
A vulnerability classified as problematic has been found in WCMS 11. Rated medium severity (CVSS 4.8), this vulnerabilit
WCMS v0.3.2 has a CSRF vulnerability, with resultant directory traversal, to modify index.html via the /wex/html.php?fin
A vulnerability was found in WCMS up to 8.3.11. Rated medium severity (CVSS 6.3), this vulnerability is remotely exploit
EUVD-2026-92044
GHSA-f4pc-vr7p-jfm7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB