dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32428

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in Ays Pro Popup Like box ays-facebook-popup-likebox allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Popup Like box: from n/a through <= 3.7.7.

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

This is a Missing Authorization (Broken Access Control) vulnerability in the Ays Pro Popup Like box WordPress plugin (ays-facebook-popup-likebox). The plugin fails to properly verify user permissions before allowing access to certain functionality or data, allowing unauthenticated or lower-privileged users to perform actions they should not have access to.

MitigationImplement proper authorization checks (capability verification and nonce validation) on all sensitive functions and AJAX endpoints within the plugin. Ensure all actions verify the current user has appropriate privileges before executing.

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

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

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 Ays Pro Popup Like box plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ays Pro Popup Like box' or 'ays-facebook-popup-likebox'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'ays-facebook-popup-likebox' or similar.
    Affected if The plugin is installed and active on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin Plugins list, find the plugin and check the version column. If not visible, open the main plugin PHP file (usually in the plugin folder root) and look for a 'Version:' header in the plugin comments.
    Affected if The installed version has not been patched for the authorization bypass vulnerability
  3. Check for unauthenticated AJAX endpoints
    Examine the plugin's main PHP file and any ajax-handling files for action hooks like 'wp_ajax_' or 'wp_ajax_nopriv_' that process sensitive operations without verifying user capabilities using functions like current_user_can() or check_ajax_referer().
    Affected if The plugin registers AJAX endpoints accessible to unauthenticated users (wp_ajax_nopriv_) without proper capability checks
  4. Inspect AJAX action handlers for authorization logic
    Review the callback functions registered to AJAX hooks. Look for whether the function validates the user's permission level before executing sensitive operations such as modifying settings, accessing user data, or performing database changes.
    Affected if AJAX handlers execute without verifying the user has appropriate permissions (e.g., administrator-level capabilities)
  5. Test access to sensitive plugin functions
    Attempt to access plugin functionality or trigger AJAX actions while logged out or as a low-privilege user (subscriber). Compare the plugin's behavior against the expected behavior where such actions should be denied.
    Affected if Unauthenticated or low-privilege users can successfully perform actions that should require higher privileges

A user is affected if the Ays Pro Popup Like box plugin is installed and its AJAX endpoints or sensitive functions can be accessed or executed by unauthenticated or low-privilege users without proper authorization validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks (capability verification and nonce validation) on all sensitive functions and AJAX endpoints within the plugin. Ensure all actions verify the current user has appropriate privileges before executing.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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