LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41343: registerFont in FontMetrics.php in Dompdf before 2.0.1 allows remote file inclusion because a URI validatio...

registerFont in FontMetrics.php in Dompdf before 2.0.1 allows remote file inclusion because a URI validation failure does not halt font registration, as demonstrated by a @font-face rule.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Dompdf before 2.0.1 could continue registering a font even after URI validation failed. In applications that render attacker-controlled HTML or CSS to PDF, this can expose sensitive local files through remote file inclusion behavior. The source bundle does not show active exploitation.

Executive priority

Prioritize remediation for internet-facing or customer-facing PDF generation because the impact is sensitive file disclosure. If Dompdf is only used with trusted templates and patched versions, urgency is lower but still warrants verification.

Technical view

CVE-2022-41343 affects Dompdf registerFont handling in FontMetrics.php before 2.0.1. A URI validation failure did not halt font registration, demonstrated through @font-face CSS. CVSS 3.1 is 7.5, network reachable, low complexity, unauthenticated, with high confidentiality impact.

Likely exposure

Exposure is most likely in web apps or background services using Dompdf before 2.0.1 to render untrusted or user-influenced HTML/CSS into PDFs. The provided affected-product metadata is incomplete, so confirm by dependency inventory rather than product names alone.

Exploitation context

The bundle includes a public issue, pull request, release reference, and third-party write-up. CISA KEV status is false, and no provided source states active exploitation. Treat as plausible where Dompdf rendering accepts attacker-controlled CSS.

Researcher notes

The strongest evidence is the CVE description and upstream GitHub issue, PR, and 2.0.1 release. Affected metadata in the bundle is sparse, so version-based validation is essential. Do not assume compromise without logs or a cited exploitation source.

Mitigation direction

  • Upgrade Dompdf to version 2.0.1 or later.
  • Review the Dompdf 2.0.1 release notes and linked fix.
  • Avoid rendering untrusted HTML or CSS until patched.
  • Restrict PDF generation inputs to trusted templates where feasible.
  • Check vendor guidance if upgrading is not immediately possible.

Validation and detection

  • Inventory applications for dompdf/dompdf versions before 2.0.1.
  • Identify PDF routes, jobs, or APIs that accept user-controlled HTML or CSS.
  • Confirm dependency lockfiles and deployed artifacts use the patched version.
  • Review whether external users can influence @font-face CSS reaching Dompdf.
  • Document any compensating input restrictions pending upgrade.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-552: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41343 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-41343Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-552

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-552 · source CWE mapping

Files or Directories Accessible to External Parties

Files or Directories Accessible to External Parties represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs