How severe is CVE-2017-16807?

CVE-2017-16807 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-16807?

CVE-2017-16807 affects the following packages: getkirby/cms (Packagist), getkirby/cms (Packagist), getkirby/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-16807?

Update getkirby/cms to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-16807 is resolved across your whole dependency graph.

How do I detect CVE-2017-16807 in my Packagist dependencies?

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

How do I mitigate CVE-2017-16807 if there is no patch (or I can't update yet)?

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.

Is CVE-2017-16807 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2017-16807, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-16807?

CVE-2017-16807 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-16807?

CVE-2017-16807 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2017-16807 published, and has it been updated?

CVE-2017-16807 was published on November 13, 2017 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2017-16807 — cms

MEDIUM

CVE-2017-16807 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in getkirby/cms. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for getkirby/cms — see the affected versions and patch details below.

Kirby XSS Vulnerability

Also known asGHSA-275c-v3rc-xghx

Published

Nov 13, 2017

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

3 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

3 pkgs affected

🐘getkirby/cms🐘getkirby/cms🐘getkirby/cms

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

A cross-site Scripting (XSS) vulnerability in Kirby Panel before 2.3.3, 2.4.x before 2.4.2, and 2.5.x before 2.5.7 exists when displaying a specially prepared SVG document that has been uploaded as a content file.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`getkirby/cms`	all versions	2.3.3`composer require getkirby/cms:^2.3.3`
🐘Packagist	`getkirby/cms`	≥ 2.4&&< 2.4.2	2.4.2`composer require getkirby/cms:^2.4.2`
🐘Packagist	`getkirby/cms`	≥ 2.5&&< 2.5.7	2.5.7`composer require getkirby/cms:^2.5.7`

Affected Products

1 product · 3 configurations

Application

panelgetkirby

≥ 2.5.0 && < 2.5.7

range

Exploits & PoCs

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

EDB-43140webappsphp✓ Verified

Kirby CMS < 2.5.7 - Cross-Site Scripting

by Ishaq Mohammed · Nov 13, 2017

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for getkirby/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update getkirby/cms to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-16807 is resolved across your whole dependency graph.
Workarounds
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

O3 Security · Impact-Aware SCA

Is CVE-2017-16807 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 3 public proof-of-concept references are listed on this page.

Timeline

First exploit

Nov 13, 2017

Disclosed

Nov 13, 2017

Last updated

Oct 24, 2026

Identifiers

CVE-2017-16807

GHSA-275c-v3rc-xghx

References

Advisorynvd.nist.gov · CVE 2017 16807 Webgetkirby.com · kirby 2 5 7 Webexploit-db.com Evidencepacketstormsecurity.com · KirbyCMS Cross Site Scripting Evidenceexploit-db.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting getkirby/cms are rated as high or higher (top: high).

CVE-2026-75592CVE-2026-69127CVE-2026-71415CVE-2026-75594CVE-2026-49274CVE-2026-50188CVE-2026-54004CVE-2026-54005

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2017-16807 — cms

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2017-16807 in your dependencies?