Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2023-35161 is a critical-severity Improper Neutralization of Alternate XSS Syntax (CWE-87) vulnerability in Xwiki Xwiki. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
XWiki Platform, a generic wiki platform, contains a cross-site scripting vulnerability in the AppWithinMinutes/DeleteApplication page that permits JavaScript injection through a crafted URL parameter such as xredirect. The flaw has existed since version 6.2-milestone-1 and allows an attacker to supply arbitrary script content that executes in the context of another user’s session.
An unauthenticated remote attacker can exploit the issue simply by inducing a victim to visit a maliciously constructed link, achieving reflected XSS with a CVSS score of 9.6. Successful exploitation can result in theft of sensitive data, session hijacking, or full compromise of the affected user’s account within the wiki instance.
Public advisories and patches indicate that the vulnerability was fixed in XWiki 14.10.5 and 15.1-rc-1; the corresponding commits and GitHub Security Advisory GHSA-4xm7-5q79-3fch document the code changes that sanitize the redirect parameter and close the injection vector.
EPSS for this CVE rose from lower values to a peak of 0.3788 on 2025-01-22 before receding to the current 0.1556, indicating a period of increased exploitation interest well after initial disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1693
Vulnerability Data
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Users are able to forge an URL with a payload allowing to inject Javascript in the page (XSS). It's possible to exploit the…
more
DeleteApplication page to perform a XSS, e.g. by using URL such as: > xwiki/bin/view/AppWithinMinutes/DeleteApplication?appName=Menu&resolve=true&xredirect=javascript:alert(document.domain). This vulnerability exists since XWiki 6.2-milestone-1. The vulnerability has been patched in XWiki 14.10.5 and 15.1-rc-1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.
Validates web inputs to reject script-related content that could produce XSS.
Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper input neutralization and output encoding to prevent alternate XSS syntax.
Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper neutralization of alternate script syntax, directly eliminating CWE-87.
Security testing catches residual XSS but does not itself implement the neutralization controls.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.
Secure SDLC mandates input validation and output encoding that directly prevent alternate XSS syntax.
Application security requirements explicitly call for neutralization of untrusted input to block XSS variants.