LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3122: GD Mail Queue <= 3.9.3 - Unauthenticated Stored Cross-Site Scripting via Email

The GD Mail Queue plugin for WordPress is vulnerable to Stored Cross-Site Scripting via email contents in versions up to, and including, 3.9.3 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
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-3122 affects the GD Mail Queue WordPress plugin through version 3.9.3. An unauthenticated attacker may place malicious script content into queued email data, which can later run in a victim's browser when the injected page is viewed.

Executive priority

Treat this as a high-priority WordPress plugin remediation item, not an emergency zero-day based on the provided evidence. Prioritize public sites and admin-facing workflows where stored script execution could affect privileged users.

Technical view

The issue is stored cross-site scripting caused by insufficient input sanitization and output escaping of email contents in GD Mail Queue. CVSS is 7.2 with network access, low attack complexity, no privileges, and changed scope. The cited weakness is CWE-79.

Likely exposure

Exposure is likely limited to WordPress sites using GD Mail Queue version 3.9.3 or earlier, especially where unauthenticated users can influence email content processed by the plugin.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The risk is still meaningful because stored XSS can persist and execute when a user views affected plugin-controlled content.

Researcher notes

The source bundle identifies unauthenticated stored XSS via email contents and references a WordPress plugin changeset. It does not provide exploit details, confirmed exploitation, or complete remediation notes, so validation should focus on version exposure and vendor guidance.

Mitigation direction

  • Identify all WordPress sites running GD Mail Queue.
  • Update GD Mail Queue beyond version 3.9.3 if a vendor-patched release is available.
  • If no patched release is available, disable or remove the plugin.
  • Review vendor and WordPress plugin guidance before restoring affected workflows.
  • Limit administrative access until affected instances are remediated.

Validation and detection

  • Confirm installed GD Mail Queue versions across WordPress estates.
  • Check whether any instance is version 3.9.3 or earlier.
  • Review plugin pages that display queued email content for unexpected script-like content.
  • Verify remediation by confirming the plugin version is no longer vulnerable.
  • Check logs for suspicious unauthenticated submissions around email-generation workflows.
Prepared
Confidence
medium
Sources
4

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-2023-3122 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-3122Attack 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
gdragonGD Mail Queue0unaffected
Weakness

CWE details

CWE-79

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