CVE-2018-14520 json
Kirby CMS 2.5.12 Cross-site Scripting
published 2022-08-24 4 y ago modified 2026-06-17 4 mo ago also GHSA-h3w2-qg2r-c7mf , EUVD-2022-6562
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
An issue was discovered in Kirby 2.5.12. The application allows malicious HTTP requests to be sent in order to trick a user into adding web pages.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- zaranshaikh.blogspot.com http://zaranshaikh.blogspot.com/2018/07/cross-site-request-forgery-kirby-cms.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | getkirby/cms | <=2.5.12 |
no fix listed |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
zaranshaikh.blogspot.com
/2018/07/cross-site-request-forgery-kirby-cms.html
web, exploit, third-party-advisory
-
exploit-db.com
/exploits/45068
web, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2018-14520
advisory
-
github.com
/getkirby/kirby
package
Sources
- CVE List CVE-2018-14520
- GitHub Advisory GHSA-h3w2-qg2r-c7mf
- NVD CVE-2018-14520
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.