How severe is CVE-2022-0955?

CVE-2022-0955 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-2022-0955?

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

How do I fix CVE-2022-0955?

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

How do I detect CVE-2022-0955 in my Packagist dependencies?

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-0955 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0955, 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-0955?

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

CVE-2022-0955 is classified as Cross-site Scripting (XSS) (CWE-79). 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-0955 published, and has it been updated?

CVE-2022-0955 was published on March 24, 2022 and was last updated on October 28, 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-2022-0955 — data-hub

MEDIUMFix: pimcore/data-hub@15d5b57

CVE-2022-0955 is a medium-severity (CVSS 6.5) Cross-site Scripting (XSS) vulnerability in pimcore/data-hub. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for pimcore/data-hub — see the affected versions and patch details below.

Cross-site Scripting (XSS) - Stored in pimcore/data-hub

Also known asBIT-pimcore-2022-0955GHSA-vc5r-xfc4-4x22

Published

Mar 24, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% 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/data-hub

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 Datahub prior to 1.2.4 is vulnerable to stored cross-site scripting. An admin user accessing Datahub triggers the attack, which may result in the user's cookie being stolen.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`pimcore/data-hub`	all versions	1.2.4`composer require pimcore/data-hub:^1.2.4`

Affected Products

1 product · 1 configurations

Application

data-hubpimcore

< 1.2.4

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.

Cross-site Scripting (XSS) - Stored in GitHub repository pimcore/data-hu…

huntr.devNVDMar 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/data-hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/data-hub to 1.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0955 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Pimcore Datahub prior to 1.2.4 is vulnerable to stored cross-site scripting. An admin user accessing Datahub triggers the attack, which may result in the user's cookie being stolen.

O3 Security · Impact-Aware SCA

Is CVE-2022-0955 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

Local

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Mar 24, 2022

First exploit

Mar 29, 2022

5 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-0955

GHSA-vc5r-xfc4-4x22

BIT-pimcore-2022-0955

References

Advisorygithub.com · CVE 2022 0955.json Advisorynvd.nist.gov · CVE 2022 0955 Fixgithub.com · 15d5b57af2466eebd3bbc531ead5dafa35d0a36e Webhuntr.dev · 708971a6 1e6c 4c51 a411 255caeba51df Packagegithub.com · data hub

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-0955 — data-hub

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-2022-0955 in your dependencies?