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

CVE-2026-57322

HIGH · 7.1 CVSS v3.1 Published 2026-06-26
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 8 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
Unauthenticated Cross Site Scripting (XSS) in weMail <= 2.1.2 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in weMail plugin versions 2.1.2 and below allows remote attackers to inject malicious scripts without authentication, likely through unsanitized user inputs in plugin forms or parameters.

MitigationUpdate weMail to the latest version (>2.1.2) to obtain the patched version, as this is an unauthenticated XSS requiring only that the plugin be installed.

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 weMail plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) or log into the WordPress admin dashboard and navigate to Plugins to confirm weMail is listed as an installed plugin
    Affected if weMail plugin is present in the WordPress installation
  2. Determine installed weMail version
    Open the main weMail plugin file (typically wp-content/plugins/wemail/wemail.php) and read the Version field from the plugin header comment block, or view the version displayed in the WordPress admin Plugins page
    Affected if Unable to determine version or version is readable from the plugin header
  3. Compare version to affected range
    Compare the installed version number to 2.1.2 using standard version comparison (e.g., 2.1.2, 2.1.1, 2.1.0, 2.0.0, 1.x.x are all <= 2.1.2)
    Affected if Installed version is 2.1.2 or any version lower than 2.1.2

If weMail plugin is installed and the version is 2.1.2 or lower, the environment is affected by this unauthenticated XSS vulnerability since the flaw exists in the plugin itself without requiring any specific configuration.

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 weMail to the latest version (>2.1.2) to obtain the patched version, as this is an unauthenticated XSS requiring only that the plugin be installed.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57322 — 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-57322 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