How severe is CVE-2022-0258?

CVE-2022-0258 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-0258?

CVE-2022-0258 affects the following packages: pimcore/pimcore (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-0258?

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

How do I detect CVE-2022-0258 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-2022-0258 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-2022-0258 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0258, including 1 in-the-wild exploitation 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-2022-0258?

CVE-2022-0258 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 76th 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-2022-0258?

CVE-2022-0258 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-2022-0258 published, and has it been updated?

CVE-2022-0258 was published on January 17, 2022 and was last updated on August 12, 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

HIGH severity

CVE-2022-0258 — pimcore

HIGHFix: pimcore/pimcore@66281c1

CVE-2022-0258 is a high-severity (CVSS 8.3) SQL Injection vulnerability in pimcore/pimcore. 1 public exploit reference exists, so weaponization risk is real. A fix is available for pimcore/pimcore — see the affected versions and patch details below.

SQL Injection in pimcore/pimcore

Also known asGHSA-vj9x-w7ch-f46p

Published

Jan 17, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-0258 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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 is vulnerable to Improper Neutralization of Special Elements used in an SQL Command

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pimcorepimcore

< 10.2.8

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.

pimcore is vulnerable to Improper Neutralization of Special Elements use…

huntr.devNVDJan 2022

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 10.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0258 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 is vulnerable to Improper Neutralization of Special Elements used in an SQL Command

O3 Security · Impact-Aware SCA

Is CVE-2022-0258 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Raw vector

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

CWE Classification

CWE-89SQL Injection

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jan 17, 2022

First exploit

Jan 25, 2022

Last updated

Aug 12, 2026

Identifiers

CVE-2022-0258

GHSA-vj9x-w7ch-f46p

References

Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Webhuntr.dev Packagegithub.com

Related vulnerabilities

This CVE is high severity; 7 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 verifiedAug 12, 2026