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

CVE-2026-3090

HIGH · 7.2 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘event_type’ parameter in all versions up to, and including, 3.8.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability is only exploitable when the Post SMTP Pro plugin is also installed and its Reporting and Tracking extension is enabled.

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 · high confidence

Stored Cross-Site Scripting (XSS) vulnerability in the Post SMTP WordPress plugin allows unauthenticated attackers to inject arbitrary JavaScript via the 'event_type' parameter due to insufficient input sanitization and output escaping. The malicious payload persists in the database and executes when users access affected pages. Exploitation requires both the Post SMTP Pro plugin and its Reporting and Tracking extension to be enabled.

MitigationUpdate Post SMTP plugin to version 3.8.1 or later. As a temporary measure, disable the Reporting and Tracking extension in Post SMTP Pro. Audit and clean the database to remove any injected malicious 'event_type' values.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Post SMTP plugin is installed
    Go to WordPress admin > Plugins and locate Post SMTP. Note the installed version number from the plugin list.
    Affected if Post SMTP plugin is not installed means not affected.
  2. Confirm Post SMTP Pro is installed
    Check if the Pro version of the plugin is active. In WordPress admin, look for Post SMTP menu items that indicate Pro features, or check the plugin file header for 'Pro' designation.
    Affected if Only the free version is installed means not affected; exploitation requires the Pro plugin.
  3. Verify Reporting and Tracking extension is enabled
    In WordPress admin, navigate to Post SMTP > Extensions or Settings. Look for the Reporting and Tracking extension and confirm its status is active/enabled.
    Affected if The Reporting and Tracking extension is disabled means not affected; both Pro and this extension must be enabled.
  4. Compare installed version to fixed release
    Locate the installed Post SMTP version (from Plugins page or plugin header file). Compare it to version 3.8.1. Versions before 3.8.1 are affected.
    Affected if Installed version is 3.8.0 or earlier.
  5. Inspect database for suspicious event_type entries
    Query the WordPress database (via phpMyAdmin or wp-cli) for the event_type meta key in the postmeta table, or check any custom tables created by Post SMTP. Look for unexpected JavaScript tags, script elements, or XSS payloads in the event_type values.
    Affected if Malicious or unexpected JavaScript code is found in event_type database records.

User is affected if Post SMTP Pro with Reporting and Tracking extension is active AND the plugin version is 3.8.0 or earlier, or if malicious event_type values already exist in the database.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Post SMTP plugin to version 3.8.1 or later. As a temporary measure, disable the Reporting and Tracking extension in Post SMTP Pro. Audit and clean the database to remove any injected malicious 'event_type' values.

Recommended fix Moderate confidence

Post SMTP version 3.8.1 or later (latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Post SMTP' plugin
  4. Check if the current version is 3.8.0 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version, or manually download the updated plugin from wordpress.org and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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