Skip to content
vulnerability

CVE-2016-10033

9.8
Critical
KEV · Exploited in wildEPSS 100%Patch available

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra parameters to the mail command and consequently execute arbitrary code via a \" (backslash double quote) in a crafted Sender property.

exploited
Yes, in CISA KEV since 7 Jul 2025fix by 28 Jul 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 99.7%
Published 30 Dec 2016Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: partlyAV · networkCWE-88· Common Weakness

Can a WAF block it? Partly. The attack involves sending a crafted HTTP request with a Sender property containing a backslash double quote to exploit the mailSend function. This unusual character sequence in the Sender field could be detected by a WAF, but it might overlap with some legitimate uses, making filtering only partly reliable. A custom WAF rule can filter Sender property containing a backslash double quote sequence, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.

What a custom rule would match: Sender property containing a backslash double quote sequence

Also consider: patch · custom WAF rule

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2016-10033 being exploited?

Yes. CVE-2016-10033 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2016-10033?

CVE-2016-10033 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2016-10033?

Yes. A fix has been recorded for CVE-2016-10033. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2016-10033 affect?

CVE-2016-10033 affects phpmailer_project:phpmailer, wordpress:wordpress, joomla:joomla\!. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
phpmailer_project:phpmailerwordpress:wordpressjoomla:joomla\!

public exploits

Public exploit code: 9 on Exploit-DB · 2 Metasploit modules · 17 GitHub proofs of concept · 1 Nuclei template

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 17 Jul 2025 (SSVC 2.0.3).

timeline

  1. 25 Dec 2016First public exploit or proof of concept
  2. 30 Dec 2016Published · 6 days later
  3. 7 Jul 2025Added to CISA KEV (exploited in the wild) · 3,110 days (about 9 years) later
  4. 17 Jul 2025CISA SSVC assessment: exploitation active · 10 days later
  5. 28 Jul 2025CISA remediation due date (US federal agencies) · 11 days later
  6. 21 Oct 2025CVE record last updated · 86 days (about 3 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
22 references in the CVE record: 9 exploits, 13 links
Show 14 more

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved