CVE-2018-19047
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 · uneditedmPDF through 7.1.6, if deployed as a web application that accepts arbitrary HTML, allows SSRF, as demonstrated by a '<img src="http://192.168' substring that triggers a call to getImage in Image/ImageProcessor.php. NOTE: the software maintainer disputes this, stating "If you allow users to pass HTML without sanitising it, you're asking for trouble.
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 · high confidencemPDF through 7.1.6 contains a Server-Side Request Forgery (SSRF) vulnerability in its ImageProcessor.php component. When the library processes HTML input containing img tags with arbitrary URLs, it makes server-side requests to fetch those resources without proper validation, allowing attackers to make the server connect to internal infrastructure or external targets.
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<= 7.1.6CVSS 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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 mPDF library in your environmentSearch for the mpdf directory or namespace in your codebase, typically found under vendor/mpdf/mpdf, or check your composer.json for a mpdf dependency entryAffected if mPDF library is present in your project dependencies
-
Identify the installed mPDF versionCheck the version file within the mPDF directory (such as version.php or the version constant in Mpdf.php), or look up the version in your composer.lock file under the mpdf package entryAffected if The version number is 7.1.6 or lower, or the version cannot be determined but mPDF is present
-
Determine if your application passes HTML with img tags to mPDFReview your codebase for calls to mPDF methods (such as WriteHTML, SetHTMLHeader, or Image) where the input may contain user-supplied or untrusted img elements with src attributesAffected if Your application passes HTML containing img tags to mPDF for PDF generation and the image URLs are not validated before being processed
-
Check if image URLs can be controlled by external usersTrace the data flow from user input (HTTP request parameters, form fields, uploaded content) to the mPDF image processing function in ImageProcessor.phpAffected if External or untrusted users can influence the src attribute of img tags passed to mPDF, enabling them to supply arbitrary URLs
You are affected if your environment runs mPDF version 7.1.6 or lower and your application processes HTML containing img tags with user-controlled URLs through mPDF without validation.
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 dataImplement strict input validation/sanitization on any user-supplied HTML before passing it to mPDF, or configure network segmentation/firewall rules to restrict outbound connections from the server to prevent internal resource access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19047 — 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-2018-19047 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