LiveActive security incident?Get immediate response
CVE Record

CVE-2023-33999: WordPress WP Mail Log plugin <= 1.0.2 - Reflected Cross Site Scripting (XSS) vulnerability

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in WPVibes WP Mail Log allows DOM-Based XSS. This issue affects WP Mail Log: from n/a through 1.0.2.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress WP Mail Log plugin through version 1.0.2. A crafted interaction could cause script to run in a user’s browser. The main business risk is account misuse or data exposure if a privileged WordPress user is tricked into opening malicious content.

Executive priority

Treat this as a high-priority WordPress plugin exposure review, especially for externally managed or business-critical sites. Urgency is driven by administrator-targeted XSS risk, not confirmed mass exploitation in the provided sources.

Technical view

Sources describe a reflected/DOM-based cross-site scripting issue caused by improper input neutralization during page generation. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, scope changed, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress sites with WPVibes WP Mail Log installed at version 1.0.2 or earlier. The source bundle does not identify other affected products, CPEs, or platforms.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires user interaction, so phishing or administrator browsing to attacker-controlled content is the likely risk pattern, but no exploit details are provided in the bundle.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The title says reflected XSS while the description says DOM-based XSS; analysts should preserve that distinction until vendor details clarify the affected sink and trigger.

Mitigation direction

  • Inventory WordPress sites for the WP Mail Log plugin and installed version.
  • Check WPVibes and Patchstack guidance for a fixed version or official mitigation.
  • Update, disable, or remove the plugin if no supported safe version is available.
  • Prioritize sites where administrators frequently access untrusted links or public submissions.

Validation and detection

  • Confirm whether WP Mail Log is installed on each WordPress instance.
  • Record the exact plugin version and flag versions through 1.0.2.
  • Review vendor and Patchstack entries for current remediation status.
  • Check security monitoring for unusual administrator browser or WordPress activity.
Prepared
Confidence
medium
Sources
3

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-33999 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.1 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
0ADP providers
2Source 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2023-33999Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WPVibesWP Mail Logwp-mail-log, n/aunaffected
Weakness

CWE details

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.