CVE-2026-16268
Unauthenticated SSRF in Newsletters WordPress plugin allows server-side requests to arbitrary hosts
Is CVE-2026-16268 being exploited?
Not confirmed. CVE-2026-16268 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.
How severe is CVE-2026-16268?
CVE-2026-16268 is rated High with a CVSS score of 8.2. 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-2026-16268?
Yes. A fix has been recorded for CVE-2026-16268. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16268 affect?
CVE-2026-16268 affects Newsletters WordPress plugin < 4.16, WordPress sites with the plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16268?
Update plugin to 4.16+ immediately; or remove plugin and apply WAF/SSRF mitigations
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SSRF: attacker can force server to fetch attacker URLs, reach internal hosts, scan/pivot, and potentially exfiltrate data.
Immediate action required
- affected< 4.16
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.