CVE-2020-13625

CVE-2020-13625 is a high-severity vulnerability in Phpmailer Project Phpmailer with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-116.

Key facts

Description

PHPMailer before 6.1.6 contains an output escaping bug when the name of a file attachment contains a double quote character. This can result in the file type being misinterpreted by the receiver or any mail relay processing the message.

Frequently asked questions

What is CVE-2020-13625?
PHPMailer before 6.1.6 contains an output escaping bug when the name of a file attachment contains a double quote character. This can result in the file type being misinterpreted by the receiver or any mail relay processing the message.
How severe is CVE-2020-13625?
CVE-2020-13625 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2020-13625 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-13625?
CVE-2020-13625 primarily affects Phpmailer Project Phpmailer. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-13625?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-13625 published?
CVE-2020-13625 was published on 2020-06-08 and last updated on 2026-06-17.

References

Affected products (6)

More vulnerabilities in Phpmailer Project Phpmailer

All CVEs affecting Phpmailer Project Phpmailer →

Other CWE-116 vulnerabilities

Browse all CWE-116 vulnerabilities →