vciy

CVE-2023-50720

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 Solr search discloses email addresses of users

CVE-2023-507204 of 4 sources documented this
33

rank 33 = 15 + 13 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.59119  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 20

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 33

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 28

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$709,000over the next 30 days, if this record is yours
Movement-$27,900on 2026-01-15, the last material move, 5 months before this reading
Basisassumeda published average, not your estate

$709,000 = $4.99M incident cost x 0.24048551839932833 exposure x 0.59119 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.59119EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.00045 to 0.59119 across 31 observations. arc-rules@v1

Foresight · where to check next

CVE-2016-2388CVE-2016-6415Cisco AdaptiveminioCisco IOS XRcheckpoint Check50720

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

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 · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-200 Exposure of Sensitive Information to an Unauthorized Actorreceipt
Published consequencesCWE-200: Confidentiality: Read Application Data[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.5; xwiki 15.5.2receipt
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 CNA5.3 MEDIUMreceipt
CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.59119 · top 0.93% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes31 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productxwiki-platformreceipt
Published rangesxwiki < 14.10.5; xwiki >= 15.0 < 15.5.2; xwiki 15.6; xwiki 15.7receipt

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.

What it is stated by the CNA

XWiki Platform is a generic wiki platform. Prior to versions 14.10.15, 15.5.2, and 15.7-rc-1, the Solr-based search in XWiki discloses the email addresses of users even when obfuscation of email addresses is enabled. To demonstrate the vulnerability, search for `objcontent:email*` using XWiki's regular search interface. This has been fixed in XWiki 14.10.15, 15.5.2 and 15.7RC1 by not indexing email address properties when obfuscation is enabled. There are no known workarounds for this vulnerability. receipt

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
weakness
CWE-200
affected versions
xwiki < 14.10.5; xwiki >= 15.0 < 15.5.2; xwiki 15.6; and 1 more, listed in full below
also scored by
[email protected] 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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

Dated events

2024-12-17EPSS moved 0.01 to 0.072025-03-29EPSS moved 0.09 to 0.642026-06-15EPSS moved 0.43 to 0.59

Movement the material steps

16 Dec 20230.00045
17 Mar 20250.09407 · scoring model v2025.03.14
29 Mar 20250.63587 · crossed 0.10 and 0.50
30 Mar 20250.09407 · crossed 0.10 and 0.50
15 Apr 20250.30357 · crossed 0.10
5 May 20250.42999
15 May 20250.52036 · crossed 0.50
18 Nov 20250.10906 · crossed 0.50
21 Nov 20250.514 · crossed 0.50
15 Jan 20260.49077 · crossed 0.50
15 Jun 20260.59119 · crossed 0.50 · scoring model v2026.06.15

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

Show all 31 observations
16 Dec 20230.00045
20 Dec 20230.00052
19 Jun 20240.00748
21 Jun 20240.00749
10 Jul 20240.00921
2 Aug 20240.01060
13 Aug 20240.00939
17 Sep 20240.01054
28 Sep 20240.00923
21 Oct 20240.01094
14 Nov 20240.00969
17 Dec 20240.06971
21 Dec 20240.03806
16 Jan 20250.03971
17 Mar 20250.09407
18 Mar 20250.05398
23 Mar 20250.09407
24 Mar 20250.05398
28 Mar 20250.09407
29 Mar 20250.63587
30 Mar 20250.09407
15 Apr 20250.30357
5 May 20250.42999
15 May 20250.52036
25 May 20250.514
18 Nov 20250.10906
21 Nov 20250.514
15 Jan 20260.49077
4 Feb 20260.49722
6 Jun 20260.43167
15 Jun 20260.59119

31 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.59119Published2023-12-15Index as of2026-06-15

Exploit probability more than doubled between 2025-03-28 and 2025-03-29 (0.09407 → 0.63587) and the record had been public for 2 years, 6 months when this index was last written.

Published 2023-12-15 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2016-2388matches 8 of 8KEV listed · 2016receipt
CVE-2016-6415matches 7 of 8KEV listed · 2016receipt
CVE-2020-3259 · Cisco Adaptive Security Appliance (ASA)…matches 7 of 9KEV listed · 2020receipt
CVE-2023-28432 · miniomatches 7 of 9KEV listed · 2023receipt
CVE-2022-20821 · Cisco IOS XR Softwarematches 7 of 9KEV listed · 2022receipt
CVE-2024-24919 · checkpoint Check Point Quantum Gateway, Spark…matches 6 of 9KEV listed · 2024receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

11146 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

xwiki-platform

Of the 10 records in this family, this is the only one whose title names addresses.

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

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.