dbcve.org
Manage Notification E MailsWordPress extension · Freeamigos

CVE-2022-34654

HIGH · 8.8 CVSS v3.1 Published 2022-11-28
Fix available
A fix is available. Upgrade to 1.8.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the Manage Notification E-mails WordPress plugin versions 1.8.2 and below. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions, such as modifying notification email settings, without their knowledge.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify these nonces server-side before processing any state-changing requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Manage Notification E MailsWordPress extension
Affected:< 1.8.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Freeamigos Manage Notification E Mails plugin is installed
    Go to WordPress admin dashboard > Plugins and look for 'Freeamigos Manage Notification E Mails' or 'Freeamigos Manage Notification E-Mails' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    Click on the plugin in the WordPress plugins list to view its details, or inspect the plugin main file header for the Version comment (typically in the plugin's main PHP file in wp-content/plugins/)
    Affected if The version listed is 1.8.2 or lower (anything below 1.8.3)
  3. Verify the plugin handles notification email settings
    Access the plugin settings page in WordPress admin (usually under Settings or a dedicated menu item for this plugin) and confirm there are forms or AJAX actions related to managing notification email configurations
    Affected if The plugin settings page is accessible and contains forms for modifying email addresses or notification settings
  4. Inspect plugin code for missing nonce verification
    Examine the plugin's PHP files (especially form handlers and AJAX endpoints) for presence of wp_verify_nonce or check_admin_referer calls. CSRF protection is absent if these nonce verification functions are missing before processing state-changing requests
    Affected if The plugin processes settings/email modifications without verifying WordPress nonces, meaning no nonce check is found in the form handling code

You are affected if the Freeamigos Manage Notification E Mails plugin version 1.8.2 or lower is installed and its email settings forms lack WordPress nonce verification, allowing attackers to trick authenticated administrators into unknowingly modifying notification email configurations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.8.3 or later
Fixed in 1.8.3
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX endpoints within the plugin, and verify these nonces server-side before processing any state-changing requests.

Recommended fix Moderate confidence

1.8.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Manage Notification E-mails' plugin
  4. 4. Check if an update to version 1.8.3 or later is available
  5. 5. If update available, click 'Update Now' to upgrade to the fixed version
  6. 6. If no automatic update is available, manually download version 1.8.3 or later from the WordPress plugin repository
  7. 7. Deactivate the current plugin version
  8. 8. Delete the current plugin files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Manage Notification E Mails Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34654 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data