LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34654: WordPress Manage Notification E-mails Plugin <= 1.8.2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) in Virgial Berveling's Manage Notification E-mails plugin <= 1.8.2 on WordPress.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress Manage Notification E-mails plugin up to 1.8.2. An attacker could try to trick a logged-in user into making an unintended change. The published impact is limited to integrity, with no stated confidentiality or availability loss.

Executive priority

Treat this as a moderate WordPress hygiene item. It is not described as actively exploited, but affected sites should be identified and remediated because CSRF can enable unauthorized configuration changes through a targeted user.

Technical view

CVE-2022-34654 is CWE-352 in Virgial Berveling's Manage Notification E-mails WordPress plugin <= 1.8.2. The CVSS 3.1 score is 4.3, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The bundle does not identify the vulnerable endpoint, exact action, or fixed version.

Likely exposure

Exposure is limited to WordPress sites that have the Manage Notification E-mails plugin installed at version 1.8.2 or earlier. Sites not using this plugin are not indicated as affected.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires user interaction, consistent with a CSRF condition.

Researcher notes

Public data is sparse. The record confirms CSRF, affected plugin family, version boundary <= 1.8.2, and low integrity impact. It does not provide endpoint details, proof-of-concept status, fixed version, or vendor advisory detail in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for the Manage Notification E-mails plugin and version.
  • Check vendor or Patchstack guidance for a fixed release or mitigation.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict administrator access and reinforce anti-phishing controls for WordPress users.

Validation and detection

  • Confirm whether the plugin is installed and active on each WordPress site.
  • Record installed plugin versions and identify any version <= 1.8.2.
  • Review vendor or Patchstack records for fixed-version availability.
  • Review recent WordPress administrative changes related to notification email settings.
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-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-2022-34654 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
4.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2022-34654Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
Virgial BervelingManage Notification E-mails (WordPress plugin)n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.