Skip to content
Fencer Vulns
medium 6.5

CVE-2022-39315 json

Kirby CMS vulnerable to user enumeration in the brute force protection

published 2022-10-18 4 y ago modified 2026-06-17 4 mo ago also GHSA-c27j-76xg-6x4f , EUVD-2022-7071

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Kirby is a Content Management System. Prior to versions 3.5.8.2, 3.6.6.2, 3.7.5.1, and 3.8.1, a user enumeration vulnerability affects all Kirby sites with user accounts unless Kirby's API and Panel are disabled in the config. It can only be exploited for targeted attacks because the attack does not scale to brute force. The problem has been patched in Kirby 3.5.8.2, Kirby 3.6.6.2, Kirby 3.7.5.1, and Kirby 3.8.1. In all of the mentioned releases, the maintainers have rewritten the affected code so that the delay is also inserted after the brute force limit is reached.

Patch / fix

  • packagist getkirby/cms 3.5.8.2, 3.6.6.2, 3.7.5.1, 3.8.1
  • getkirby kirby 3.5.8.2, 3.6.6.2, 3.7.5.1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist getkirby/cms
<3.5.8.2
>=3.6.0, <3.6.6.2
>=3.7.0, <3.7.5.1
>=3.8.0, <3.8.1
3.5.8.2
3.6.6.2
3.7.5.1
3.8.1

Affected products

  • getkirby kirby

Classification

Weakness
  • CWE-204 Observable Response Discrepancy
  • CWE-209 Generation of Error Message Containing Sensitive Information
  • CWE-668 Exposure of Resource to Wrong Sphere

References

Sources

Fencer Vulns 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.