Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-38489: Kirby vulnerable to Insufficient Session Expiration after a password change

Noroxi assessment

Priority: Monitor (action score 29/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.80% (FIRST EPSS); higher than 57% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: getkirby/cms (Packagist) 3.6.6.3, 3.7.5.2, 3.8.4.1.

Low priority for now. Upgrade to getkirby/cms (Packagist) 3.6.6.3, 3.7.5.2, 3.8.4.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Kirby is a content management system. A vulnerability in versions prior to 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6 affects all Kirby sites with user accounts (unless Kirby's API and Panel are disabled in the config). It can only be abused if a Kirby user is logged in on a device or browser that is shared with potentially untrusted users or if an attacker already maliciously used a previous password to log in to a Kirby site as the affected user. Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization. In the variation described in this advisory, it allows attackers to stay logged in to a Kirby site on another device even if the logged in user has since changed their password. Kirby did not invalidate user sessions that were created with a password that was since changed by the user or by a site admin. If a user changed their password to lock out an attacker who was already in possession of the previous password or of a login session on another device or browser, the attacker would not be reliably prevented from accessing the Kirby site as the affected user. The problem has been patched in Kirby 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6. In all of the mentioned releases, the maintainers have updated the authentication implementation to keep track of the hashed password in each active session. If the password changed since the login, the session is invalidated. To enforce this fix even if the vulnerability was previously abused, all users are logged out from the Kirby site after updating to one of the patched releases.

HighCVSS 7.3 · v3.1—No exploit Fix available
Published
Jul 27, 2023
Updated
Jun 17, 2026
EPSS
0.8% · 57th percentile

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
29 / 40 · 7.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.3
CNA · GitHub_M
7.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-38489

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
getkirbykirby

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • getkirby kirby3.5.0 and later · before 3.5.8.3
  • getkirby kirby3.6.0 and later · before 3.6.6.3
  • getkirby kirby3.7.0 and later · before 3.7.5.2
  • getkirby kirby3.8.0 and later · before 3.8.4.1
  • getkirby kirby3.9.0 and later · before 3.9.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • getkirby kirby

    • < 3.5.8.3, >= 3.6.0, < 3.6.6.3, >= 3.7.0, < 3.7.5.2, >= 3.8.0, < 3.8.41, >= 3.9.0, < 3.9.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistgetkirby/cmsfrom 3.6.0 · before 3.6.6.33.6.6.3
Packagistgetkirby/cmsfrom 3.7.0 · before 3.7.5.23.7.5.2
Packagistgetkirby/cmsfrom 3.8.0 · before 3.8.4.13.8.4.1
Packagistgetkirby/cmsfrom 3.9.0 · before 3.9.63.9.6
Packagistgetkirby/cmsbefore 3.5.8.33.5.8.3

Other highest-scoring records for the same primary product.

  • CVE-2023-38490Kirby XML External Entity (XXE) vulnerability in the XML data handler
    41Plan
  • CVE-2026-44177Kirby: Pre-authentication path traversal and PHP file inclusion during user lookup
    36Monitor
  • CVE-2026-54003Kirby: External Initialization of the Panel on reverse proxy setups with the `Forwarded` header
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-39315Oct 25, 2022 · Kirby CMS vulnerable to user enumeration in the brute force protection
    21Monitor
  • ← EarlierCVE-2023-38488Jul 27, 2023 · Kirby vulnerable to field injection in the KirbyData text storage handler
    35Monitor
  • Later →CVE-2023-38491Jul 27, 2023 · Kirby vulnerable to Cross-site scripting (XSS) from MIME type auto-detection of uploaded files
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:getkirby/cms3.5.8.3Package registry (OSV)
Packagist:getkirby/cms3.6.6.3Package registry (OSV)
Packagist:getkirby/cms3.7.5.2Package registry (OSV)
Packagist:getkirby/cms3.8.4.1Package registry (OSV)
Packagist:getkirby/cms3.9.6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records