vciy

CVE-2023-35161

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

XWiki Platform vulnerable to reflected cross-site scripting via xredirect parameter in DeleteApplication page

CVE-2023-351614 of 4 sources documented this
21

rank 21 = 1 + 15 + 1 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.02377  ·  without this subject the record ranks 20

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.1, from NVD  ·  without this subject the record ranks 6

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-03-16  ·  without this subject the record ranks 20

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 17

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$119,000over the next 30 days, if this record is yours
Movement+$350,000on 2025-11-18, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$119,000 = $4.99M incident cost x 1 exposure x 0.02377 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.02377EPSSNOT IN KEVas of 2026-09-20
Severity9.7 CRITICALreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
RISING10Risen from 0.00045 to 0.02377 across 29 observations. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
GitHub_M9.7 CRITICALreceipt
NVD6.1 MEDIUMreceipt
What it costs
GitHub_MComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
NVDPartial confidentiality and integrity loss, with impact beyond the vulnerable componentreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running xwiki-platform? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-87 Improper Neutralization of Alternate XSS Syntaxreceipt
Published consequencesCWE-87: Confidentiality, Integrity, Availability: Read Application Data, Execute Unauthorized Code or Commands[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchxwiki 14.10.5receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA9.7 CRITICALreceipt
CVSS, NVD6.1 MEDIUMreceipt
Exploit probability0.02377 · top 17% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes29 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productxwiki-platformreceipt
Published rangesxwiki >= 6.2.1 < 14.10.5; xwiki 6.2receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires user interactionxwiki-platformCWE-87 weaknessAdjacent componentsscope changeFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-87scope changedata compromise

What it is stated by the CNA

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 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. receipt

NVD's analysis a second authority

severity
6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
weakness
CWE-87; CWE-79
affected versions
xwiki >= 6.2.1 < 14.10.5; xwiki 6.2
also scored by
[email protected] 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

The CNA scored it 9.7 and NVD 6.1. Both are shown because both were published; we do not pick one.

check it yourself github.com github.com jira.xwiki.org jira.xwiki.org receipt

Dated events

2024-07-08EPSS moved 0.00 to 0.462026-06-15EPSS moved 0.16 to 0.02

Movement the material steps

24 Jun 20230.00045
8 Jul 20240.46180 · crossed 0.10
25 Jul 20240.51076 · crossed 0.50
17 Dec 20240.44929 · crossed 0.50
17 Mar 20250.1039 · scoring model v2025.03.14
29 Mar 20250.46363
30 Mar 20250.1039
15 Apr 20250.03375 · crossed 0.10
18 Nov 20250.1039 · crossed 0.10
15 Jun 20260.02143 · crossed 0.10 · scoring model v2026.06.15
23 Jun 20260.02377

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 29 observations
24 Jun 20230.00045
1 Jul 20230.00075
6 Jan 20240.00085
9 Feb 20240.00105
23 May 20240.00111
29 Jun 20240.00086
8 Jul 20240.46180
12 Jul 20240.49420
25 Jul 20240.51076
10 Oct 20240.51156
24 Oct 20240.51559
20 Nov 20240.54625
3 Dec 20240.52666
17 Dec 20240.44929
13 Jan 20250.37879
12 Mar 20250.49623
17 Mar 20250.1039
18 Mar 20250.10217
23 Mar 20250.1039
24 Mar 20250.10217
28 Mar 20250.1039
29 Mar 20250.46363
30 Mar 20250.1039
15 Apr 20250.03375
18 Nov 20250.1039
21 Nov 20250.12078
16 Mar 20260.15561
15 Jun 20260.02143
23 Jun 20260.02377

29 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.02377Published2023-06-23Index as of2026-06-23

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.1039 → 0.46363) and the record had been public for 3 years when this index was last written.

Published 2023-06-23 receipt · Index as of 2026-06-23 derived

Siblings and hubs

Records related to this one

Its defect family

xwiki-platform

Of the 5 records in this family that state one, this holds the highest EPSS percentile: 0.82728.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2023-35161.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.