How severe is CVE-2014-2383?

No CVSS score has been assigned to CVE-2014-2383 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-2383?

CVE-2014-2383 affects the following packages: dompdf/dompdf (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-2383?

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

How do I detect CVE-2014-2383 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-2014-2383 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2014-2383?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-2383 can be triaged on real exposure rather than presence alone.

Is CVE-2014-2383 actively exploited in the wild?

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

CVE-2014-2383 has an EPSS (Exploit Prediction Scoring System) score of 39.2%, placing it in the 99th 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-2014-2383?

CVE-2014-2383 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2014-2383?

A Nuclei detection template exists for CVE-2014-2383, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2014-2383 published, and has it been updated?

CVE-2014-2383 was published on April 28, 2014 and was last updated on April 10, 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

CVE-2014-2383 — dompdf/dompdf

Fix: dompdf/dompdf@23a6939

CVE-2014-2383 is a Information Exposure vulnerability in dompdf/dompdf. 1 public exploit reference exists, so weaponization risk is real. A fix is available for dompdf/dompdf — see the affected versions and patch details below.

DOMPDF Arbitrary File Read

Also known asGHSA-qr6q-w4gj-3865

Published

Apr 28, 2014

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

39.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.php in dompdf before 0.6.1, when DOMPDF_ENABLE_PHP is enabled, allows context-dependent attackers to bypass chroot protections and read arbitrary files via a PHP protocol and wrappers in the input_file parameter, as demonstrated by a php://filter/read=convert.base64-encode/resource in the input_file parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dompdf/dompdf`	≥ 0.6.0&&< 0.6.1	0.6.1`composer require dompdf/dompdf:^0.6.1`

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-33004webappsphp✓ Verified

dompdf 0.6.0 - 'dompdf.php?read' Arbitrary File Read

by Portcullis · Apr 24, 2014

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 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2383 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-2383 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-2383. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect CVE-2014-2383

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2014-2383 -u https://target

Template: Dompdf < v0.6.0 - Local File Inclusion
Severity: medium
Impact: The vulnerability can lead to unauthorized access to sensitive files, remote code execution, and compromise of the affected system.
Remediation: Upgrade Dompdf to a version higher than v0.6.0 to mitigate the vulnerability.

Template by ProjectDiscovery nuclei-templates (0x_Akoko, akincibor, ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-2383 in your dependencies?

O3 Security finds CVE-2014-2383 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works