Cross-Site Scripting
2 records66.7%First: 2025. Latest: 2026.
Plugin security history
The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with SiteGround Email Marketing, published between 2025 and 2026.
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 |
|---|---|---|
| 2025 | 1 | |
| 2026 | 2 |
| Severity | Records | Share |
|---|---|---|
| High | 1 | 33.3% |
| Medium | 2 | 66.7% |
First: 2025. Latest: 2026.
First: 2026. Latest: 2026.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
1.7.61.7.2Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-1.7.5 | SiteGround Email Marketing <= 1.7.5 - Unauthenticated Stored Cross-Site Scripting | July 8, 2026 | 1.7.6 | High |
*-1.7.5 | SiteGround Email Marketing <= 1.7.5 - Missing Authorization | June 25, 2026 | 1.7.6 | Medium |
*-1.7.1 | SiteGround Email Marketing <= 1.7.1 - Authenticated (Contributor+) Stored Cross-Site Scripting | September 30, 2025 | 1.7.2 | Medium |
Selected source records
Published: July 8, 2026
Published: June 25, 2026
Published: September 30, 2025
Published: July 8, 2026
Published: September 30, 2025
Published: June 25, 2026
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.