dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14446

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Popup Builder (Easy Notify Lite) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the easynotify_cp_reset() function in all versions up to, and including, 1.1.37. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset plugin settings to their default values.

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 Easy Notify Lite WordPress plugin fails to enforce authorization checks on the easynotify_cp_reset() function, allowing any authenticated user with Subscriber-level permissions or higher to reset all plugin settings to their default values. This broken access control vulnerability enables low-privileged users to modify plugin configuration data without proper capability verification.

MitigationUpdate the Easy Notify Lite plugin to version 1.1.38 or later which includes proper capability validation on the reset function. If no update is available, consider removing the plugin or adding access control via web application firewall rules until a patch is released.

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
None
Integrity
Low
Availability
Low

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

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. Locate Easy Notify Lite plugin
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Notify Lite' or check the /wp-content/plugins/ directory for an easynotify-lite folder
    Affected if The plugin is installed
  2. Determine installed version
    In WordPress admin Plugins list, find the version number under Easy Notify Lite, or open the main plugin file (easynotify-lite.php) and look for the 'Version' header comment
    Affected if Version is present and is below 1.1.38
  3. Verify vulnerable function exists
    In the plugin directory, locate the file containing easynotify_cp_reset() function and check if it includes a capability check (such as current_user_can() with an admin-level capability) before executing the reset logic
    Affected if The function exists and lacks proper capability validation (no current_user_can() or similar authorization check)
  4. Check for existing user accounts
    In WordPress admin, go to Users to confirm there are any users with Subscriber-level or higher roles
    Affected if Any authenticated users exist in the system (even low-privileged subscribers could exploit this if the vulnerable plugin version is present)

Your environment is affected if Easy Notify Lite is installed with a version lower than 1.1.38 and any authenticated user accounts exist on the WordPress site.

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 Easy Notify Lite plugin to version 1.1.38 or later which includes proper capability validation on the reset function. If no update is available, consider removing the plugin or adding access control via web application firewall rules until a patch is released.

Recommended fix High confidence

Version 1.1.38 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Popup Builder (Easy Notify Lite)' plugin
  4. 4. Check if an update is available and update to version 1.1.38 or higher
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin to upload the updated version directly from the WordPress plugin repository
  6. 6. After updating, verify the plugin is functioning correctly and settings are as expected

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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