dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1720

HIGH · 8.8 CVSS v3.1 Published 2026-03-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 WowOptin: Next-Gen Popup Maker – Create Stunning Popups and Optins for Lead Generation plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the 'install_and_active_plugin' function in all versions up to, and including, 1.4.24. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install and activate arbitrary plugins.

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 WowOptin plugin for WordPress contains a broken access control vulnerability where the 'install_and_active_plugin' function lacks a capability check. This allows any authenticated user with Subscriber-level access or higher to install and activate arbitrary plugins on the WordPress site, leading to full site compromise.

MitigationUpdate the plugin to version 1.4.25 or later which includes proper capability verification. If an update is unavailable, disable the plugin or restrict user registrations as an interim measure 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
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 WowOptin plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WowOptin' or check the wp-content/plugins directory for wowoptin folder
    Affected if WowOptin plugin is present on the site
  2. Check installed WowOptin version
    In WordPress admin_plugins list, find WowOptin and note the version number displayed, or read the version in wowoptin/readme.txt or wowoptin/wowoptin.php header
    Affected if Version is below 1.4.25
  3. Determine if user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership - Anyone can register' setting, or inspect wp_options table for 'users_can_register' value = 1
    Affected if User registration is enabled (anyone can register as a subscriber)
  4. Check for existing Subscriber-level users
    In WordPress admin > Users, look for users with 'Subscriber' role, or query wp_users joined with wp_usermeta where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'
    Affected if Any Subscriber-level user accounts exist on the site

User is affected if WowOptin plugin is installed with a version below 1.4.25 AND user registration is open OR existing Subscriber accounts are present, allowing privilege escalation via the unauthenticated plugin installation function.

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 version 1.4.25 or later which includes proper capability verification. If an update is unavailable, disable the plugin or restrict user registrations as an interim measure until a patch is released.

Recommended fix Moderate confidence

Version 1.4.25 or later

  1. 1. Log in to WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WowOptin: Next-Gen Popup Maker plugin
  4. 4. Check if an update to version 1.4.25 or higher is available
  5. 5. If update available, click 'Update Now' to install the patched version
  6. 6. Verify the update was successful by confirming the new version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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