How severe is CVE-2022-28368?

CVE-2022-28368 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-28368?

CVE-2022-28368 affects the following packages: dompdf/dompdf (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-28368?

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

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

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

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

Yes. There are 4 known exploit references for CVE-2022-28368, including 1 documented proof-of-concept exploit on Exploit-DB and 2 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-2022-28368?

CVE-2022-28368 has an EPSS (Exploit Prediction Scoring System) score of 83.9%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2022-28368?

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

CVE-2022-28368 was published on April 3, 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

CRITICAL severity

CVE-2022-28368 — dompdf

CRITICALFix: dompdf/dompdf@4c70e10

CVE-2022-28368 is a critical-severity (CVSS 9.8) Cross-site Scripting (XSS) vulnerability in dompdf/dompdf. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for dompdf/dompdf — see the affected versions and patch details below.

Remote code injection in dompdf/dompdf

Also known asGHSA-x752-qjv4-c4hc

Published

Apr 3, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

83.9%probability of exploitation in next 30 days

Very High Risk0.00%

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

🐘dompdf/dompdf

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

Dompdf is an HTML to PDF converter. Dompdf before 1.2.1 allows remote code execution via a .php file in the src:url field of an @font-face Cascading Style Sheets (CSS) statement (within an HTML input file).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dompdf/dompdf`	all versions	1.2.1`composer require dompdf/dompdf:^1.2.1`

Affected Products

1 product · 1 configurations

Application

dompdfdompdf_project

< 1.2.1

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

Dompdf 1.2.1 - Remote Code Execution (RCE)

by Ravindu Wickramasinghe · Apr 6, 2023

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 dompdf/dompdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dompdf/dompdf to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28368 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

O3 Security · Impact-Aware SCA

Is CVE-2022-28368 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

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

OpenSSF Scorecard

Package health score

dompdf

2.7/10

Code-Review1/10

Maintained6/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Apr 3, 2022

First exploit

Apr 6, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2022-28368

GHSA-x752-qjv4-c4hc

References

Advisorygithub.com · CVE 2022 28368.json Advisorynvd.nist.gov · CVE 2022 28368 Advisorygithub.com · GHSA x752 qjv4 c4hc Fixgithub.com · 4c70e1025bcd9b7694b95dd552499bd83cd6141d Fixgithub.com Reportgithub.com Articlesnyk.io · security alert php pdf library dompdf rce Webpacketstormsecurity.com · Dompdf 1.2.1 Remote Code Execution Webpackagist.org · dompdf Webgithub.com · CVE 2022 28368.yaml Websnyk.io · security alert php pdf library dompdf rce Packagegithub.com · php goof Packagegithub.com · dompdf

Related vulnerabilities

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

CVE-2026-55555CVE-2026-59941CVE-2026-56722CVE-2026-59942CVE-2026-59943CVE-2026-55554CVE-2021-3902CVE-2021-3838

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-28368 — dompdf

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