LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3082: Post SMTP <= 2.5.7 - Unauthenticated Stored Cross-Site Scripting via Email

The Post SMTP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 2.5.7 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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-3082 affects the WordPress Post SMTP plugin through version 2.5.7. Untrusted email content can be stored without proper sanitization and later run as script when someone views the affected page. This can expose data or alter actions in the viewer’s browser, especially for privileged WordPress users.

Executive priority

Prioritize remediation on production WordPress sites because unauthenticated input can lead to browser script execution for site users. The highest business concern is compromise of privileged admin sessions or data viewed in affected plugin pages.

Technical view

The issue is stored cross-site scripting, CWE-79, caused by insufficient input sanitization and output escaping of email contents. It is rated CVSS 7.2. The source bundle identifies unauthenticated injection and execution when a user accesses the injected page. Evidence does not show CISA KEV listing or active exploitation.

Likely exposure

Exposure is most likely on WordPress sites running Post SMTP versions up to and including 2.5.7, especially where email logs or email-derived content are accessible to administrators or other users.

Exploitation context

The CVE record says unauthenticated attackers can inject scripts through email contents. The provided sources do not establish active exploitation, public weaponization, or KEV status. Treat exploitability as plausible but unconfirmed in the supplied evidence.

Researcher notes

The source bundle is clear on class, affected upper version, unauthenticated injection, and CVSS. It does not provide exploit telemetry, affected route details, or a named fixed version. Validate remediation against the WordPress changeset or vendor release notes.

Mitigation direction

  • Upgrade Post SMTP to a vendor-confirmed fixed version newer than 2.5.7.
  • Review the WordPress changeset and vendor guidance for the exact fixed release.
  • Limit access to plugin email log views until remediation is complete.
  • Remove or sanitize suspicious stored email-log content after upgrade.
  • Apply normal WordPress least-privilege controls for administrator access.

Validation and detection

  • Inventory all WordPress sites using the Post SMTP plugin.
  • Confirm each installed Post SMTP version is newer than 2.5.7.
  • Review plugin email logs for suspicious script-like stored content.
  • Verify the vendor fix or changeset is present in deployed code.
  • Confirm no exposed route renders email content without escaping.
Prepared
Confidence
high
Sources
4

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-2023-3082 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
3Source 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-2023-3082Attack 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
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 links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.