Skip to main content
CVE-2024-56527VulnerabilityPublished Updated

CVE-2024-56527: tecnick tcpdf · XSS or 'Cross-site Scripting'

Affects tecnick tcpdfSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 6.8.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.8.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade tecnick/tcpdf to 6.8.0.

Affected software

ProductAffectedFixed in
Packagisttecnick/tcpdfpkg:composer/tecnick/tcpdfOther threatsAffected
  • <6.8.0
Fixed in
  • 6.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade TCPDF to version 6.8.0 or later as soon as it becomes available to ensure the Error function properly sanitizes error messages. 2. In the interim, implement manual input validation and output encoding on all error messages generated by TCPDF to neutralize potentially malicious content. 3. Employ web application firewalls (WAFs) with rules targeting common XSS payloads to detect and block exploitation attempts. 4. Conduct thorough code reviews and security testing on applications integrating TCPDF to identify and remediate any unsafe error handling or input processing. 5. Monitor logs for unusual error message patterns or spikes in PDF generation failures that could indicate exploitation attempts. 6. Educate development teams on secure coding practices related to input sanitization and error handling to prevent similar vulnerabilities. 7. Isolate PDF generation services where possible to limit the blast radius of potential attacks. 8. Maintain an incident response plan tailored to web application vulnerabilities to enable rapid containment and recovery if exploitation occurs.

Description

An issue was discovered in TCPDF before 6.8.0. The Error function lacks an htmlspecialchars call for the error message.

References

Community reviews

Loading reviews…