# CVE-2026-63092: kirby-modules License Key Disclosure via modules/activate Dialog

> Authenticated users can retrieve plaintext commercial license keys via an unsecured dialog endpoint, enabling unauthorized plugin activation on other installations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-w794-j6vc-x62h

## What is CVE-2026-63092?

CVE-2026-63092 is a medium-severity vulnerability in medienbaecker kirby-modules, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

kirby-modules through 5.5.7, fixed in commit 315417e, contains an information disclosure vulnerability that allows any authenticated Kirby Panel user to retrieve the full plaintext commercial license key by sending a GET request to the modules/activate dialog endpoint. The plugin's activate dialog handler in lib/areas.php returns the complete key via ModulesLicense::readKey() without performing an administrator check, as the dialog is gated only by the access.system permission which defaults to true for all non-admin roles, enabling attackers to use the disclosed key to activate the plugin on arbitrary third-party installations.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-63092?


## How do I fix CVE-2026-63092?

No fix has been published for CVE-2026-63092 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63092 being exploited?

There is no known exploitation of CVE-2026-63092 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63092 and fix it if it is affected.

What it is: CVE-2026-63092 is a medium-severity vulnerability in medienbaecker kirby-modules, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63092 in the wild and no public exploit code.

Affected product: medienbaecker kirby-modules. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63092/ (Markdown: https://insights.sbomify.com/CVE-2026-63092/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63092
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63092
- OSV: https://osv.dev/vulnerability/CVE-2026-63092

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63092/
Summaries are generated and may contain mistakes; the official description above is the record.