Categories
CVE-2020-13625

Vulnerability in phpmailer/phpmailer (CVE-2020-13625)

Summary

Vulnerability in phpmailer/phpmailer (CVE-2020-13625). Data can be tampered with by attackers. Exploitable via filename.html. Mitigation: upgrade to 6.1.6 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-13625 has been found in phpmailer/phpmailer.
Attackers can target a specific entry point like filename.html over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade phpmailer/phpmailer to 6.1.6 or later.
If unsure, ask your IT team or search "phpmailer/phpmailer CVE-2020-13625" on the vendor's site.

CVE-2020-13625 (phpmailer/phpmailer) — CWE-116
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: filename.html / attachment.tmp
Patched: 6.1.6 — apply immediately
Workaround: Reject or filter names and filenames containing double quote (") characters before passing them to attachment functions such as addAttachment().
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-116) exists in phpmailer/phpmailer. Attackers reach the vulnerable code path via filename.html without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of phpmailer/phpmailer. Attack surface: filename.html / attachment.tmp.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 6.1.6.

🛡️ Workaround

Workaround: Reject or filter names and filenames containing double quote (") characters before passing them to attachment functions such as addAttachment().

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phpmailer/phpmailer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'phpmailer/phpmailer' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で phpmailer/phpmailer を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Reject or filter names and filenames containing double quote (`"`) characters before passing them to attachment functions such as `addAttachment()`.

    パッチが適用されるまでの応急処置として、Reject or filter names and filenames containing double quote (") characters before passing them to attachment functions such as addAttachment(). を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade phpmailer/phpmailer to 6.1.6

    ステージング環境で 6.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist phpmailer/phpmailer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.6"}]}]
Bitnami phpmailer
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.1.6"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details