LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38325: User Activation Email <= 1.3.0 Reflected Cross-Site Scripting

The User Activation Email WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the uae-key parameter found in the ~/user-activation-email.php file which allows attackers to inject arbitrary web scripts, in versions up to and including 1.3.0.

MediumCVSS 6.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-38325 is a reflected cross-site scripting issue in the User Activation Email WordPress plugin through version 1.3.0. A malicious link could cause script execution in a victim's browser. The sources do not show confirmed active exploitation or a named fixed release.

Executive priority

Handle as a moderate-priority WordPress exposure. It is not marked as actively exploited in the provided sources, but public sites with the vulnerable plugin could expose users or administrators to browser-based compromise through crafted links.

Technical view

The flaw is CWE-79 reflected XSS through the uae-key parameter in user-activation-email.php. CVSS 3.1 is 6.1, with network access, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is limited to WordPress sites running the User Activation Email plugin up to and including 1.3.0, especially public sites where users or administrators can receive and open crafted links.

Exploitation context

The source bundle indicates user interaction is required. CISA KEV is false, and no cited source in the bundle confirms active exploitation. The provided evidence does not establish exploit availability beyond the vulnerability description and code reference.

Researcher notes

Evidence supports reflected XSS in plugin versions up to 1.3.0 and maps to CWE-79. The bundle includes a source-code reference but does not name a fixed version, patch commit, or confirmed exploitation. Validate against installed plugin state before escalating.

Mitigation direction

  • Inventory WordPress sites for the User Activation Email plugin and its installed version.
  • Check vendor, WordPress plugin, or Wordfence guidance for a fixed or supported release.
  • Disable or remove the plugin where it is not operationally required.
  • Prioritize remediation on public WordPress sites and administrator-facing workflows.
  • Treat WAF filtering as compensating control only, not confirmed remediation.

Validation and detection

  • Confirm whether user-activation-email is installed and active on each WordPress site.
  • Flag installations running version 1.3.0 or earlier for remediation review.
  • Review web logs for unusual requests referencing the uae-key parameter.
  • Verify remediation by confirming the vulnerable plugin version is no longer active.
  • Document any exception with business owner, exposure, and compensating controls.
Prepared
Confidence
high
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-2021-38325 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
Medium
CVSS
6.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: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
6.1CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.1Medium
CVSS 3.1 vector shape for CVE-2021-38325Attack 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: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
User Activation EmailUser Activation Email1.3.0Listed
Weakness

CWE details

CWE-79

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