NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2018-16630 — kirby

MEDIUM

CVE-2018-16630 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in getkirby/kirby. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Kirby XSS Vulnerability

Also known asGHSA-3gq5-r59m-mmv2
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk
0.00%0.35%0.71%1.06%0.2%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘getkirby/kirby

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Kirby v2.5.12 allows XSS by using the "site files" Add option to upload an SVG file.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistgetkirby/kirbyall versionsNo fix

Affected Products

1 product · 1 configurations
Application
kirbygetkirby
1 version
2.5.12
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/kirby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of getkirby/kirby for CVE-2018-16630. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Kirby v2.5.12 allows XSS by using the "site files" Add option to upload an SVG file.
O3 Security · Impact-Aware SCA

Is CVE-2018-16630 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2018-16630: kirby: Kirby XSS Vulnerability