CVE-2014-5013
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDOMPDF before 0.6.2 allows remote code execution, a related issue to CVE-2014-2383.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDOMPDF before version 0.6.2 contains a remote code execution vulnerability. This is a flaw in the PHP PDF generation library that allows attackers to execute arbitrary code on the server, likely through the same or similar PHP object injection mechanism as the related CVE-2014-2383.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.6.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate dompdf installation in your projectSearch for dompdf directory in your application's vendor folder, or check composer.json for a dompdf dependency entry under 'require'.Affected if dompdf is present in the codebase.
-
Identify the installed dompdf versionOpen the VERSION file in the dompdf directory, or check the version string in dompdf.php or lib/class.pdf.php. If using Composer, run 'composer show dompdf/dompdf' to see the installed version.Affected if The version displayed is less than 0.6.2.
-
Confirm the PHP object injection endpoint is accessibleReview your application code to determine if dompdf is exposed through a web-accessible script that accepts user input and passes it to dompdf for PDF rendering.Affected if User-controlled input can reach dompdf's rendering functions without sanitization.
-
Check for unsafe unserialize usageSearch the dompdf source code (particularly in lib/frame_tree.cls.php or related classes) for 'unserialize' calls that process input without prior validation.Affected if The code contains unserialize() calls operating on data that could be influenced by an attacker.
Your environment is affected if dompdf version is below 0.6.2 and user input can reach dompdf's PDF generation functionality without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.6.2
Upgrade DOMPDF to version 0.6.2 or later to remediate this vulnerability. If upgrading is not immediately feasible, restrict network access to the PDF generation functionality and ensure proper input sanitization.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-5013 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data