Skip to content
Fencer Vulns
medium 5.4

CVE-2018-14059 json

Pimcore XSS Vulnerability

published 2018-08-24 8 y ago modified 2026-06-17 4 mo ago also GHSA-276r-24xq-hwg8 , EUVD-2022-1927

cvss
5.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
1
Exploit-DB

Summary

Pimcore allows XSS via Users, Assets, Data Objects, Video Thumbnails, Image Thumbnails, Field-Collections, Objectbrick, Classification Store, Document Types, Predefined Properties, Predefined Asset Metadata, Quantity Value, and Static Routes functions.

Patch / fix

  • packagist pimcore/pimcore 5.3.0

Timeline

  1. First public exploit (EDB-45208)
  2. Published

Exploit prediction

3.12% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-45208 Pimcore 5.2.3 - SQL Injection / Cross-Site Scripting / Cross-Site Request Forgery webapps, 2018-08-16
  • seclists.org http://seclists.org/fulldisclosure/2018/Aug/13 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/148954/Pimcore-5.2.3-CSRF-Cross-Site-Scripting-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
  • sec-consult.com https://www.sec-consult.com/en/blog/advisories/sql-injection-xss-csrf-vulnerabilities-in-pimcore-software/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N
GitHub 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist pimcore/pimcore
<5.3.0
5.3.0

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

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.