dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-2933

HIGH · 8.8 CVSS v3.1 Published 2025-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
The Email Notifications for Updates plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the awun_import_settings() function in all versions up to, and including, 1.1.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site. CVE-2025-26741 is likely a duplicate of this issue.

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 · high confidence

The Email Notifications for Updates WordPress plugin lacks a capability check on the awun_import_settings() function, allowing any authenticated user with Subscriber-level access to call this function and modify arbitrary WordPress options. Attackers can enable user registration and change the default registration role to Administrator, gaining full admin access to the site.

MitigationUpdate the plugin to the latest patched version immediately. If no patch is available, remove the plugin and review user accounts for unauthorized administrative accounts.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify the plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Email Notifications for Updates' or check the wp-content/plugins directory for a plugin folder with 'email-notifications' or similar naming
    Affected if The plugin is installed and active
  2. Check the plugin version
    In WordPress Admin > Plugins, find the plugin and view the version number. Compare against any known affected versions if documented in the plugin changelog
    Affected if The installed version has not been patched and falls within the vulnerable version range
  3. Identify subscriber-level accounts
    In WordPress Admin > Users, filter by the Subscriber role to see all subscriber accounts
    Affected if Any subscriber accounts exist on the site
  4. Verify user registration settings
    In WordPress Admin > Settings > General, check if 'Membership' > 'Anyone can register' is enabled
    Affected if User registration is enabled on the site
  5. Check default new user role
    In WordPress Admin > Settings > General, check the 'Default Role' dropdown for new user registration
    Affected if The default role is set to Administrator
  6. Audit admin-level accounts
    In WordPress Admin > Users, review all users with Administrator role, looking for unfamiliar or recently created accounts that you did not create
    Affected if There are administrator accounts you did not create or do not recognize

A user is affected if the plugin is installed, any subscriber-level accounts exist, and either user registration is enabled or unauthorized administrator accounts are present.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version immediately. If no patch is available, remove the plugin and review user accounts for unauthorized administrative accounts.

Recommended fix High confidence

Version 1.1.7 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Email Notifications for Updates' plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, manually download version 1.1.7 or later from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number matches 1.1.7 or higher under Plugins > Installed Plugins
  7. Review site options (Settings > General) to ensure no unauthorized changes were made to user registration settings

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2933 — 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-2025-2933 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