setasign/fpdi vulnerabilities
FPDI is a collection of PHP classes facilitating developers to read pages from existing PDF documents and use them as templates in FPDF. Because it is also possible to use FPDI with TCPDF, there are no fixed dependencies defined. Please see suggestions for packages which evaluates the dependencies automatically.
- Registry
- Composer
- Latest
- 2.6.10
- License
- MIT
2 known advisories
The latest version, 2.6.10, is not affected by any of them. Projects on older versions may be.
composer require setasign/fpdi:^2.6.10Is your project on an affected setasign/fpdi?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for setasign/fpdi
FPDI: Memory Exhaustion and Endless Loop in FPDI leads to Denial of Service
- Affected
- <2.6.7
- Fixed in
- 2.6.7
FPDI allows Memory Exhaustion (OOM) in PDF Parser which leads to Denial of Service
- Affected
- <2.6.4
- Fixed in
- 2.6.4
Is your setasign/fpdi version vulnerable?
- setasign/fpdi 2.6No known advisories in 2.6.10
- setasign/fpdi 2.52 advisories in 2.5.0
- setasign/fpdi 2.42 advisories in 2.4.1
- setasign/fpdi 2.32 advisories in 2.3.7
- setasign/fpdi 2.22 advisories in 2.2.0
- setasign/fpdi 2.12 advisories in 2.1.1
- setasign/fpdi 1.62 advisories in 1.6.2
- setasign/fpdi 1.52 advisories in 1.5.4
Which of your client projects still run an old setasign/fpdi?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.