Skip to content
Fencer Intel
critical 9.1

CVE-2022-2073 in the critical feed json

Code Injection in getgrav/grav

published 4y ago modified 4mo ago also GHSA-cxgw-r5jg-7xwq , EUVD-2022-6030

cvss
9.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
10.9%
EPSS 10.9% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Code Injection in GitHub repository getgrav/grav prior to 1.7.34.

Patch / fix

  • packagist getgrav/grav 1.7.34
  • getgrav getgrav/grav 1.7.34

Is CVE-2022-2073 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

10.91% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/3ef640e6-9e25-4ecb-8ec1-64311d63fe66 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 9.1 CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist getgrav/grav
<1.7.34
1.7.34

Affected products

  • getgrav getgrav/grav

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.