dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57416

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SiteGround SiteGround Email Marketing siteground-email-marketing allows Stored XSS.This issue affects SiteGround Email Marketing: from n/a through <= 1.7.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored Cross-site Scripting (XSS) vulnerability in the SiteGround Email Marketing WordPress plugin allows authenticated or unauthenticated attackers to inject malicious JavaScript code through unsanitized input fields. This injected script executes in the browsers of users who view the affected pages, potentially enabling session hijacking, credential theft, or defacement.

MitigationUpdate SiteGround Email Marketing to the latest patched version. If no update is available, implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) and output encoding (esc_js, wp_kses) for all user-supplied data before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify SiteGround Email Marketing plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'SiteGround Email Marketing' or 'siteground email marketing'. Confirm the plugin appears in the list.
    Affected if The plugin is installed and active on the WordPress site
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Find SiteGround Email Marketing and view the version number displayed beneath the plugin name. Compare this to any version information from the plugin developer or security advisory.
    Affected if The installed version matches or falls within an affected version range if specified by the plugin vendor
  3. Identify exposed input fields
    Navigate to the plugin settings or any public-facing forms created by SiteGround Email Marketing (e.g., subscription forms, contact forms, email signup fields). Inspect the HTML of these forms by right-clicking and selecting 'Inspect' to identify all input fields that accept user data.
    Affected if The plugin exposes any user-facing input fields that accept data without visible sanitization indicators
  4. Test for unsanitized output in form submissions
    Submit a test string containing HTML or JavaScript characters (e.g., <script>alert('test')</script> or <img src=x onerror=alert(1)>) through the plugin's input fields. Then view the page where this data would be displayed and inspect the page source to see if the input is rendered as raw text or executed as code.
    Affected if The submitted test payload is rendered as executable HTML/JavaScript rather than being escaped or encoded
  5. Review plugin source code for sanitization functions
    Access the plugin files via FTP or file manager. Navigate to the plugin directory (typically wp-content/plugins/siteground-email-marketing or similar). Examine PHP files that handle form submissions and output, looking for functions like sanitize_text_field, esc_html, esc_attr, esc_js, or wp_kses.
    Affected if The plugin code lacks proper sanitization functions on input handling or output rendering routines

A site is affected if SiteGround Email Marketing plugin is installed, contains input fields accessible to users, and those fields or their output lack proper sanitization, allowing stored scripts to execute in visitor browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SiteGround Email Marketing to the latest patched version. If no update is available, implement proper input sanitization using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) and output encoding (esc_js, wp_kses) for all user-supplied data before rendering.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57416 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data