Information Disclosure
1 record33.3%First: 2014. Latest: 2014.
Plugin security history
The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with Email Newsletter, published between 2014 and 2015.
Dataset last synchronized: 2026-08-03 00:31:25 UTC
At a glance
Use this history
A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.
| Year | Records | Relative volume |
|---|---|---|
| 2014 | 1 | |
| 2015 | 2 |
| Severity | Records | Share |
|---|---|---|
| Critical | 1 | 33.3% |
| High | 2 | 66.7% |
First: 2014. Latest: 2014.
First: 2015. Latest: 2015.
First: 2015. Latest: 2015.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
20.13.79.0Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-20.13.6 | Email Newsletter <= 20.13.6 - Reflected Cross-Site Scripting | November 24, 2015 | 20.13.7 | High |
*-20.15 | Email Newsletter <= 20.15 - Unauthenticated SQL Injection | June 25, 2015 | Not supplied | Critical |
*-8.0 | Email Newsletter <= 8.0 - Sensitive Information Disclosure | August 1, 2014 | 9.0 | High |
Selected source records
Published: November 24, 2015
Published: June 25, 2015
Published: August 1, 2014
Published: June 25, 2015
Published: August 1, 2014
Published: November 24, 2015
Published: June 25, 2015
Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.
Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.
This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.