LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44777: WordPress Email Tracker plugin <= 5.2.6 - Cross-Site Request Forgery (CSRF) vulnerabilities leading to single or bulk e-mail entries deletion

Cross-Site Request Forgery (CSRF) vulnerabilities leading to single or bulk e-mail entries deletion discovered in Email Tracker WordPress plugin (versions <= 5.2.6).

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

Security readout for executives and security teams

Plain-English summary

This issue affects the Email Tracker WordPress plugin through version 5.2.6. A malicious site could trick a logged-in WordPress user into triggering unwanted deletion of tracked email entries. The business impact is loss or manipulation of email tracking records, not server takeover based on the provided sources.

Executive priority

Treat this as a moderate priority where the plugin supports sales, compliance, or operational recordkeeping. It does not indicate full site compromise, but unauthorized deletion of tracking records can affect evidence quality and business workflows.

Technical view

CVE-2021-44777 is a CSRF flaw in Prashant Baldha's Email Tracker WordPress plugin versions <= 5.2.6. The reported impact is single or bulk deletion of email entries. CVSS 3.1 is 5.4 with network access, low complexity, required user interaction, and low confidentiality/integrity impact.

Likely exposure

Exposure is limited to WordPress sites using Email Tracker plugin version 5.2.6 or earlier. Risk depends on privileged or relevant users being logged into WordPress and induced to visit attacker-controlled content.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The flaw is CSRF, so exploitation requires victim interaction and an authenticated WordPress session capable of deleting email entries.

Researcher notes

The provided evidence identifies CWE-352 and deletion of email entries as the impact. Fix details are not present in the source bundle, so remediation should be tied to vendor or Patchstack guidance rather than assumed version thresholds beyond <= 5.2.6.

Mitigation direction

  • Inventory WordPress sites for the Email Tracker plugin and record installed versions.
  • If version is <= 5.2.6, check vendor guidance for an update or safe replacement.
  • Disable the plugin where email tracking records are business-critical until remediated.
  • Review backups and retention for email tracking records.
  • Limit administrative WordPress sessions on untrusted browsing contexts.

Validation and detection

  • Confirm whether Email Tracker is installed on each WordPress instance.
  • Verify the installed plugin version is not within the affected <= 5.2.6 range.
  • Review plugin changelog and Patchstack entry for vendor-confirmed remediation details.
  • Check audit logs or backups for unexpected single or bulk email entry deletion.
  • Confirm deletion actions are protected by anti-CSRF controls in the deployed version.
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-352: 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-44777 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
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2021-44777Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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
Prashant BaldhaEmail Tracker (WordPress plugin)<= 5.2.6Listed
Weakness

CWE details

CWE-352

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