How severe is CVE-2018-14058?

CVE-2018-14058 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-14058?

CVE-2018-14058 affects the following packages: pimcore/pimcore (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-14058?

Update pimcore/pimcore to 5.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14058 is resolved across your whole dependency graph.

How do I detect CVE-2018-14058 in my Packagist dependencies?

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

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

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2018-14058 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2018-14058, including 1 documented proof-of-concept exploit on Exploit-DB and 5 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-2018-14058?

CVE-2018-14058 has an EPSS (Exploit Prediction Scoring System) score of 28.6%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2018-14058?

CVE-2018-14058 is classified as SQL Injection (CWE-89). 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-2018-14058 published, and has it been updated?

CVE-2018-14058 was published on August 17, 2018 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-2018-14058 — pimcore

MEDIUM

CVE-2018-14058 is a medium-severity (CVSS 6.5) SQL Injection vulnerability in pimcore/pimcore. 6 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for pimcore/pimcore — see the affected versions and patch details below.

Pimcore SQLi Vulnerability

Also known asGHSA-q4hw-c66h-4xqc

Published

Aug 17, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

6 known

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

EPSS Exploitation Probability

via FIRST.org ↗

28.6%probability of exploitation in next 30 days

Moderate Risk-0.33%

Lower risk than most CVEs98th percentile — riskier than 98% 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

1 pkg affected

🐘pimcore/pimcore

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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pimcore/pimcore`	all versions	5.3.0`composer require pimcore/pimcore:^5.3.0`

Affected Products

1 product · 1 configurations

Application

pimcorepimcore

< 5.3.0

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-45208webappsphp

Pimcore 5.2.3 - SQL Injection / Cross-Site Scripting / Cross-Site Request Forgery

by SEC Consult · Aug 16, 2018

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 pimcore/pimcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/pimcore to 5.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14058 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2018-14058 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-89SQL Injection

Weaponization

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

Timeline

First exploit

Aug 16, 2018

Disclosed

Aug 17, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-14058

GHSA-q4hw-c66h-4xqc

References

Advisorynvd.nist.gov · CVE 2018 14058 Webexploit-db.com Websec-consult.com · sql injection xss csrf vulnerabilities in pimcore software Evidencepacketstormsecurity.com · Pimcore 5.2.3 CSRF Cross Site Scripting SQL Injection Evidenceseclists.org Evidenceexploit-db.com Evidencesec-consult.com · sql injection xss csrf vulnerabilities in pimcore software

Related vulnerabilities

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

CVE-2026-55416CVE-2026-55634CVE-2026-55220CVE-2026-55072CVE-2026-11407CVE-2026-5394CVE-2026-44739CVE-2026-45703

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2018-14058 — pimcore

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-2018-14058 in your dependencies?