CVE-2022-39315
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKirby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUser enumeration vulnerability in Kirby CMS login API allows attackers to identify valid usernames through timing differences or distinct error responses. The lack of a delay after reaching the brute force limit enables targeted user enumeration attacks. Patched versions insert a delay after the brute force limit is reached.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.5.8.2>= 3.6.0, < 3.6.6.2>= 3.7.0, < 3.7.5.1= 3.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Kirby versionCheck the composer.json file in the Kirby root directory for the 'getkirby/composer-install' or 'getkirby/cms' version entry, or look in the index.php file for a version constantAffected if The installed version falls into any of these ranges: < 3.5.8.2, >= 3.6.0 and < 3.6.6.2, >= 3.7.0 and < 3.7.5.1, or equals 3.8.0
-
Verify the login API endpoint is exposedAttempt a POST request to the /api/auth/login endpoint (or the configured API route) with any username and observe the response behavior and timingAffected if The API endpoint is accessible and responds with distinguishable messages for valid vs invalid usernames, or shows timing differences
-
Check if the Panel is publicly accessibleNavigate to the /panel/ login page and confirm it is reachable without authentication restrictionsAffected if The Panel login interface is accessible from the internet without IP restrictions or authentication barriers
-
Inspect response consistency for invalid usernamesSend login attempts with multiple different usernames and compare the HTTP status codes, error messages, and response times for each attemptAffected if Different usernames produce noticeably different error messages, response codes, or timing patterns that reveal which usernames are valid in the system
You are affected if your Kirby installation version is within the vulnerable ranges listed and either the API or Panel login interface is accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.5.8.23.6.6.23.7.5.1
Update to Kirby versions 3.5.8.2, 3.6.6.2, 3.7.5.1, or 3.8.1. Alternatively, disable the API and Panel if not required.
Kirby 3.8.1 (or 3.5.8.2, 3.6.6.2, or 3.7.5.1 depending on your current branch)
- 1. Identify your current Kirby version by checking the composer.json file or the kirby/composer.json file in your installation.
- 2. Based on your current version, upgrade to the corresponding fixed release:
- - If using 3.5.x series: upgrade to 3.5.8.2
- - If using 3.6.x series: upgrade to 3.6.6.2
- - If using 3.7.x series: upgrade to 3.7.5.1
- - If using 3.8.0: upgrade to 3.8.1
- 3. Run composer update to apply the new version: composer update kirby/cms --with-all-dependencies
- 4. Test your installation thoroughly after upgrading, especially login functionality and API responses.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39315 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data