vciy

CVE-2022-4060

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.

User Post Gallery <= 2.19 - Unauthenticated RCE

CVE-2022-40604 of 4 sources documented this
48

rank 48 = 21 + 25 + 0 + 2 + 0

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.42723  ·  without this subject the record ranks 27

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 23

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 48

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 46

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.13Mover the next 30 days, if this record is yours
Movement-$42,100on 2026-03-16, the last material move, 3 months before this reading
Basisassumeda published average, not your estate

$2.13M = $4.99M incident cost x 1 exposure x 0.42723 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.42723EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationpublic proof-of-conceptreceipt
Defenseno fix version held
Movementdoubled within 72hreceipt
RISING10Risen from 0.00885 to 0.42723 across 47 observations. arc-rules@v1

Foresight · where to check next

langflow-aiRejetto HTTP FileCitrix NetScalerVMware WorkspaceIvanti EPMSpring Framework4060

This record is one instance of CWE-94, improper control of generation of code ('code injection'). The index holds 7185 prior instances of this class, 79 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 User Post Gallery? 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
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-94 Improper Control of Generation of Code ('Code Injection')receipt
Published consequencesCWE-94: Access Control: Bypass Protection Mechanism; Access Control: Gain Privileges or Assume Identity; Integrity, Confidentiality, Availability: 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.

Fixed inNo fix version in held sources, as the index stood on 18 Jun 2026.
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: Proof-of-concept published · 1 public repository, 2023-09-15.

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

Authority who says so

CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.42723 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byWPScanreceipt
Recorded changes50 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productUser Post Galleryreceipt
Published rangesodude user post gallery <= 2.19receipt

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

The User Post Gallery WordPress plugin through 2.19 does not limit what callback functions can be called by users, making it possible to any visitors to run code on sites running it. receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
affected versions
odude user post gallery <= 2.19
also scored by
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself wpscan.com receipt

Dated events

2023-09-16EPSS moved 0.06 to 0.252025-03-17EPSS moved 0.40 to 0.902026-06-15EPSS moved 0.89 to 0.43

Movement the material steps

17 Jan 20230.00885
7 Mar 20230.0112 · scoring model v2023.03.01
16 Sep 20230.25321 · crossed 0.10
20 Oct 20230.37849
8 Nov 20230.01764 · crossed 0.10
26 Jul 20240.31038 · crossed 0.10
17 Mar 20250.89661 · crossed 0.50 · scoring model v2025.03.14
29 Mar 20250.90073 · crossed 0.90
30 Mar 20250.89661 · crossed 0.90
18 Jun 20250.9135 · crossed 0.90
18 Nov 20250.73044 · crossed 0.90
21 Nov 20250.90994 · crossed 0.90
16 Mar 20260.89308 · crossed 0.90
15 Jun 20260.42994 · crossed 0.50 · scoring model v2026.06.15
18 Jun 20260.42723

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

Show all 47 observations
17 Jan 20230.00885
7 Mar 20230.0112
8 Mar 20230.01120
23 Mar 20230.01059
3 May 20230.01560
8 May 20230.00931
28 May 20230.03256
5 Jun 20230.04159
29 Jun 20230.04729
9 Jul 20230.05043
4 Sep 20230.05462
15 Sep 20230.05955
16 Sep 20230.25321
7 Oct 20230.33993
20 Oct 20230.37849
8 Nov 20230.01764
12 Nov 20230.02055
17 Dec 20230.02290
23 Jan 20240.02591
5 Feb 20240.03084
18 Feb 20240.03753
9 Apr 20240.04252
22 Apr 20240.05192
15 Jun 20240.08444
28 Jun 20240.07433
11 Jul 20240.08063
26 Jul 20240.31038
8 Aug 20240.29919
6 Sep 20240.36447
20 Sep 20240.38538
17 Dec 20240.40063
17 Mar 20250.89661
29 Mar 20250.90073
30 Mar 20250.89661
18 Jun 20250.9135
10 Sep 20250.91121
26 Sep 20250.90738
11 Oct 20250.90994
18 Nov 20250.73044
21 Nov 20250.90994
14 Dec 20250.91121
28 Feb 20260.90151
16 Mar 20260.89308
30 Mar 20260.8913
6 May 20260.88723
15 Jun 20260.42994
18 Jun 20260.42723

47 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.42723Published2023-01-16Public PoC2023-09-15Index as of2026-06-18

Exploit probability more than doubled between 2023-09-15 and 2023-09-16 (0.05955 → 0.25321) and the record had been public for 3 years, 5 months when this index was last written.

Published 2023-01-16 receipt · Public PoC 2023-09-15 receipt · Index as of 2026-06-18 derived

The pattern, elsewhere

This record is one instance of CWE-94, improper control of generation of code ('code injection'). The index holds 7185 prior instances of this class, 79 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-3248 · langflow-ai langflowmatches 8 of 9KEV listed · 2025receipt
CVE-2024-23692 · Rejetto HTTP File Servermatches 8 of 9KEV listed · 2024receipt
CVE-2023-3519 · Citrix NetScaler ADCmatches 8 of 9KEV listed · 2023receipt
CVE-2022-22954 · VMware Workspace ONE Access and Identity…matches 8 of 9KEV listed · 2022receipt
CVE-2021-44529 · Ivanti EPMmatches 8 of 9KEV listed · 2021receipt
CVE-2018-1273 · Spring Frameworkmatches 8 of 9KEV listed · 2018receipt

"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

7185 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-2022-4060.

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.