LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3090: Post SMTP <= 3.8.0 - Unauthenticated Stored Cross-Site Scripting via 'event_type'

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.

HighCVSS 7.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-3090 affects the WordPress Post SMTP plugin up to version 3.8.0, but only in a specific configuration with Post SMTP Pro and its Reporting and Tracking extension enabled. An unauthenticated attacker could store malicious script content that runs when affected pages are viewed.

Executive priority

Prioritize internet-facing WordPress sites using this plugin combination. The issue is high severity and unauthenticated, but exposure is narrower than a default plugin install because it requires the Pro extension configuration.

Technical view

This is a stored cross-site scripting issue in the event_type parameter caused by insufficient input sanitization and output escaping. The CVE lists CVSS 7.2, CWE-79, network attack vector, low complexity, no privileges required, and changed scope. Exposure requires Post SMTP Pro with Reporting and Tracking enabled.

Likely exposure

Externally reachable WordPress sites using Post SMTP <= 3.8.0 are at risk only if Post SMTP Pro is installed and Reporting and Tracking is enabled.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references include Wordfence vulnerability intelligence and a WordPress plugin changeset, which may help defenders assess code-level remediation.

Researcher notes

Key constraints are important: Post SMTP <=3.8.0 alone is not sufficient per the CVE text; Pro plus Reporting and Tracking must be enabled. Do not assume active exploitation from the provided sources.

Mitigation direction

  • Inventory WordPress sites for Post SMTP plugin versions up to 3.8.0.
  • Check whether Post SMTP Pro is installed and Reporting and Tracking is enabled.
  • Update Post SMTP according to vendor or Wordfence guidance.
  • Disable Reporting and Tracking if it is not required until remediated.
  • Review administrative users and recent plugin activity for suspicious changes.

Validation and detection

  • Confirm installed Post SMTP version on each WordPress site.
  • Confirm whether Post SMTP Pro is present.
  • Confirm Reporting and Tracking extension status.
  • Review plugin changelog or changeset 3484515 for remediation evidence.
  • Retest affected pages after updating or disabling the vulnerable configuration.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3090 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-3090Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
saadiqbalPost SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App0unaffected
Weakness

CWE details

CWE-79

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs