tecnickcom/tcpdf vulnerabilities
Deprecated legacy PDF engine for PHP. Use instead tecnickcom/tc-lib-pdf.
- Registry
- Composer
- Latest
- 7.0.24
- License
- LGPL-3.0-or-later
8 known advisories
The latest version, 7.0.24, is not affected by any of them. Projects on older versions may be.
composer require tecnickcom/tcpdf:^7.0.24Is your project on an affected tecnickcom/tcpdf?
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 tecnickcom/tcpdf
TCPDF has incorrect comparison
- Affected
- <6.8.0
- Fixed in
- 6.8.0
TCPDF missing character escape on error messages
- Affected
- <6.8.0
- Fixed in
- 6.8.0
TCPDF missing certificate validation
- Affected
- <6.8.0
- Fixed in
- 6.8.0
TCPDF lacks SVG sanitization
- Affected
- <6.8.0
- Fixed in
- 6.8.0
TCPDF Local File Inclusion vulnerability
- Affected
- <6.7.6
- Fixed in
- 6.7.6
TCPDF vulnerable to Regular Expression Denial of Service
- Affected
- <6.7.5
- Fixed in
- 6.7.5
TCPDF Cross-site Scripting vulnerability
- Affected
- <6.7.4
- Fixed in
- 6.7.4
TCPDF vulnerable to attackers triggering deserialization of arbitrary data
- Affected
- <6.2.22
- Fixed in
- 6.2.22
Is your tecnickcom/tcpdf version vulnerable?
- tecnickcom/tcpdf 7.0No known advisories in 7.0.24
- tecnickcom/tcpdf 6.11No known advisories in 6.11.4
- tecnickcom/tcpdf 6.10No known advisories in 6.10.1
- tecnickcom/tcpdf 6.9No known advisories in 6.9.4
- tecnickcom/tcpdf 6.8No known advisories in 6.8.2
- tecnickcom/tcpdf 6.74 advisories in 6.7.8
- tecnickcom/tcpdf 6.67 advisories in 6.6.2
Which of your client projects still run an old tecnickcom/tcpdf?
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.