Skip to content
Fencer Vulns
medium 6.5

CVE-2018-14058 json

Pimcore SQLi Vulnerability

published 2018-08-17 8 y ago modified 2026-06-17 4 mo ago also GHSA-q4hw-c66h-4xqc , EUVD-2022-4879

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
28.6%
EPSS 28.6% chance of exploitation in 30 days, percentile 98%
public exploits
2
Metasploit, Exploit-DB

Summary

Pimcore before 5.3.0 allows SQL Injection via the REST web service API.

Patch / fix

  • packagist pimcore/pimcore 5.3.0
  • pimcore pimcore 5.3.0

Timeline

  1. First public exploit (Metasploit auxiliary/gather/pimcore_creds_sqli)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit auxiliary/gather/pimcore_creds_sqli Pimcore Gather Credentials via SQL Injection metasploit auxiliary, normal rank, 2018-08-13
  • 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 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

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

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

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.