vciy

CVE-2023-37462

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.

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in org.xwiki.platform:xwiki-platform-skin-ui

CVE-2023-374624 of 4 sources documented this
49

rank 49 = 23 + 22 + 0 + 4 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.91592  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.8, from NVD  ·  without this subject the record ranks 27

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 49

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$4.57Mover the next 30 days, if this record is yours
Movement-$614,000on 2024-12-17, the last material move, 1 year, 8 months before this reading
Basisassumeda published average, not your estate

$4.57M = $4.99M incident cost x 1 exposure x 0.91592 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.91592EPSSNOT IN KEVas of 2026-09-20
Severity10 CRITICALreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-03-17, 541 days at 0.92, as of 2026-09-09. arc-rules@v1

Foresight · where to check next

AtlassianCisco IdentityHitachi VantaraTrend MicroCVE-2022-3591437462

This record is one instance of CWE-74, improper neutralization of special elements in output used by a downstream component ('injection'). The index holds 5545 prior instances of this class, 13 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

Sources disagree here.

Severity score
GitHub_M10 CRITICALreceipt
NVD8.8 HIGHreceipt
What it costs
GitHub_MComplete confidentiality, integrity and availability loss, with impact beyond the vulnerable componentreceipt
NVDComplete confidentiality, integrity and availability lossreceipt

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 · low privileges required · no user interaction · 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-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')…receipt
Published consequencesCWE-74: Confidentiality: Read Application Data; Access Control: Bypass Protection Mechanism; Other: Alter Execution Logic; Integrity, Other: Other; Non-Repudiation: Hide Activities[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.4; xwiki 14.4.8receipt
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 CNA10 CRITICALreceipt
CVSS, NVD8.8 HIGHreceipt
Exploit probability0.91592 · top 0.19% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes45 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productxwiki-platformreceipt
Published rangesxwiki >= 7.0 < 14.4.8; xwiki >= 14.5 < 14.10.4receipt

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 low privilegesxwiki-platformCWE-74 weaknessAdjacent componentsscope changeFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-74scope 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. Improper escaping in the document `SkinsCode.XWikiSkinsSheet` leads to an injection vector from view right on that document to programming rights, or in other words, it is possible to execute arbitrary script macros including Groovy and Python macros that allow remote code execution including unrestricted read and write access to all wiki contents. The attack works by opening a non-existing page with a name crafted to contain a dangerous payload. It is possible to check if an existing installation is vulnerable. See the linked GHSA for instructions on testing an installation. receipt

Read the rest of the CNA's description

This issue has been patched in XWiki 14.4.8, 14.10.4 and 15.0-rc-1. Users are advised to upgrade. The fix commit `d9c88ddc` can also be applied manually to the impacted document `SkinsCode.XWikiSkinsSheet` and users unable to upgrade are advised to manually patch their installations.

NVD's analysis a second authority

severity
8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-74; CWE-95
affected versions
xwiki >= 7.0 < 14.4.8; xwiki >= 14.5 < 14.10.4
also scored by
[email protected] 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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

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

Dated events

2023-07-27EPSS moved 0.02 to 0.362025-03-17EPSS moved 0.48 to 0.91

Movement the material steps

15 Jul 20230.00064
27 Jul 20230.36071 · crossed 0.10
21 Oct 20230.24146
23 Nov 20230.35357
12 Mar 20240.48302
3 Apr 20240.55748 · crossed 0.50
16 Apr 20240.67678
20 May 20240.56128
2 Jun 20240.48491 · crossed 0.50
13 Jun 20240.50956 · crossed 0.50
9 Jul 20240.45359 · crossed 0.50
9 Sep 20240.50714 · crossed 0.50
17 Dec 20240.45856 · crossed 0.50
17 Mar 20250.91088 · crossed 0.50 and 0.90 · scoring model v2025.03.14
15 Jun 20260.91346 · scoring model v2026.06.15
9 Sep 20260.91592

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

Show all 45 observations
15 Jul 20230.00064
25 Jul 20230.01689
27 Jul 20230.36071
21 Oct 20230.24146
29 Oct 20230.26117
16 Nov 20230.26840
23 Nov 20230.35357
1 Dec 20230.38658
17 Dec 20230.28519
25 Dec 20230.32698
4 Jan 20240.42489
19 Jan 20240.40099
27 Jan 20240.38472
20 Feb 20240.39588
1 Mar 20240.40719
12 Mar 20240.48302
25 Mar 20240.49627
3 Apr 20240.55748
16 Apr 20240.67678
9 May 20240.65933
20 May 20240.56128
2 Jun 20240.48491
13 Jun 20240.50956
25 Jun 20240.52332
9 Jul 20240.45359
20 Jul 20240.36456
2 Aug 20240.43814
15 Aug 20240.43046
9 Sep 20240.50714
11 Dec 20240.58161
17 Dec 20240.45856
24 Dec 20240.39955
3 Feb 20250.41529
18 Feb 20250.43556
4 Mar 20250.48107
17 Mar 20250.91088
15 Apr 20250.91429
7 May 20250.91764
14 Aug 20250.91454
18 Nov 20250.91088
21 Nov 20250.91454
17 Jan 20260.90263
15 Jun 20260.91346
15 Jul 20260.91492
9 Sep 20260.91592

45 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.91592Published2023-07-14Index as of2026-09-09

Exploit probability more than doubled between 2023-07-25 and 2023-07-27 (0.01689 → 0.36071) and the record had been public for 3 years, 1 month when this index was last written.

Published 2023-07-14 receipt · Index as of 2026-09-09 derived

The pattern, elsewhere

This record is one instance of CWE-74, improper neutralization of special elements in output used by a downstream component ('injection'). The index holds 5545 prior instances of this class, 13 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2023-22527 · Atlassian Confluence Data Centermatches 7 of 10KEV listed · 2024receipt
CVE-2025-20281 · Cisco Identity Services Engine Softwarematches 7 of 10KEV listed · 2025receipt
CVE-2025-20337 · Cisco Identity Services Engine Softwarematches 7 of 10KEV listed · 2025receipt
CVE-2022-43769 · Hitachi Vantara Pentaho Business Analytics…matches 7 of 10KEV listed · 2023receipt
CVE-2020-8468 · Trend Micro Worry-Free Business Security…matches 7 of 10KEV listed · 2020receipt
CVE-2022-35914matches 6 of 9KEV listed · 2022receipt

"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

5545 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

Browse the index from here

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

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.