vciy

CVE-2022-31267

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.

Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an…

CVE-2022-312673 of 4 sources documented this
31

rank 31 = 4 + 25 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.17542  ·  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 6

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 31

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$875,000over the next 30 days, if this record is yours
Movement-$424,000on 2025-05-23, the last material move, 1 year, 2 months before this reading
Basisassumeda published average, not your estate

$875,000 = $4.99M incident cost x 1 exposure x 0.17542 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.17542EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 53 days at 0.18, as of 2026-08-07. arc-rules@v1

Foresight · where to check next

SonicWall EmailOracle PaymentsIntel StandardminioCVE-2013-0643Microsoft Windows31267

This record is one instance of CWE-269, improper privilege management. The index holds 3614 prior instances of this class, 21 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

Check a version against this record

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-269 Improper Privilege Managementreceipt
Published consequencesCWE-269: Access Control: Gain Privileges or Assume Identity[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 7 Aug 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: 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, NVD9.8 CRITICALreceipt
Exploit probability0.17542 · top 3% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymitrereceipt
Recorded changes31 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesGitblitreceipt
Published rangesgitblit 1.9.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.

What it is stated by the CNA

Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext '[email protected]\n\trole = "#admin"' value. 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
weakness
CWE-269
affected versions
gitblit 1.9.2

check it yourself github.com github.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.132025-03-23EPSS moved 0.13 to 0.392026-06-15EPSS moved 0.01 to 0.18

Movement the material steps

22 May 20220.00885
7 Mar 20230.00106 · scoring model v2023.03.01
17 Mar 20250.13342 · crossed 0.10 · scoring model v2025.03.14
23 Mar 20250.39305
24 Mar 20250.13342
23 May 20250.04848 · crossed 0.10
15 Jun 20260.17749 · crossed 0.10 · scoring model v2026.06.15
7 Aug 20260.17542

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

Show all 31 observations
22 May 20220.00885
7 Mar 20230.00106
21 Apr 20230.00118
28 May 20230.00169
23 Jun 20230.00190
1 Nov 20230.00208
12 Dec 20230.00206
17 Dec 20240.00258
25 Dec 20240.00313
3 Feb 20250.00346
1 Mar 20250.00320
17 Mar 20250.13342
23 Mar 20250.39305
24 Mar 20250.13342
29 Mar 20250.22639
30 Mar 20250.13342
23 May 20250.04848
24 May 20250.03101
8 Jun 20250.02704
1 Oct 20250.02807
27 Oct 20250.02704
28 Oct 20250.02807
14 Nov 20250.02954
18 Nov 20250.00484
21 Nov 20250.02954
16 Dec 20250.00665
27 Dec 20250.00541
28 Dec 20250.00665
13 May 20260.0064
15 Jun 20260.17749
7 Aug 20260.17542

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.17542Published2022-05-21Index as of2026-08-07

Exploit probability more than doubled between 2025-11-18 and 2025-11-21 (0.00484 → 0.02954) and the record had been public for 4 years, 2 months when this index was last written.

Published 2022-05-21 receipt · Index as of 2026-08-07 derived

The pattern, elsewhere

This record is one instance of CWE-269, improper privilege management. The index holds 3614 prior instances of this class, 21 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2021-20021 · SonicWall Email Securitymatches 8 of 8KEV listed · 2021receipt
CVE-2026-46817 · Oracle Paymentsmatches 8 of 8KEV listed · 2026receipt
CVE-2017-5689 · Intel Standard Manageabilitymatches 8 of 8KEV listed · 2017receipt
CVE-2023-28434 · miniomatches 7 of 8KEV listed · 2023receipt
CVE-2013-0643matches 7 of 8KEV listed · 2013receipt
CVE-2024-26169 · Microsoft Windows 10 Version 1809matches 6 of 8KEV 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

3614 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-31267.

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.