dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27362

MEDIUM · 6.5 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 →
74/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 kamleshyadav WP Bakery Autoresponder Addon vc-autoresponder-addon allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Bakery Autoresponder Addon: from n/a through <= 1.0.6.

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

Missing Authorization vulnerability in WP Bakery Autoresponder Addon (vc-autoresponder-addon) allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to sensitive functionality, potentially enabling unauthenticated or lower-privileged users to perform actions reserved for administrators.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive endpoints and administrative functions within the plugin. Update to a patched version if available.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify if the vc-autoresponder-addon plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Bakery Autoresponder Addon' or 'vc-autoresponder-addon' in the installed plugins list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'vc-autoresponder-addon' or similar.
    Affected if The plugin is installed and active in the WordPress environment
  2. Determine the installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its details and version number. Compare this version against any known affected versions or the latest patched version available from the vendor.
    Affected if The installed version is older than the patched version or falls within an affected version range
  3. Identify accessible admin endpoints or functions
    Review the plugin files (particularly PHP files in the plugin directory) for AJAX actions, admin_menu entries, or public function callbacks. Look for missing capability checks (current_user_can) or nonce verification (wp_verify_nonce) before sensitive operations.
    Affected if Sensitive functions lack proper current_user_can() capability checks or nonce validation
  4. Test if lower-privileged users can access admin functions
    Create or use a subscriber-level or editor-level user account and attempt to access plugin functions that should be restricted to administrators (such as sending emails, modifying autoresponder settings, or accessing configuration panels).
    Affected if Lower-privileged users can successfully perform actions intended only for administrators
  5. Check for unauthenticated access to plugin functionality
    Inspect the plugin's AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) and front-end forms. Verify whether nopriv hooks require authentication or proper capability checks.
    Affected if AJAX endpoints registered with wp_ajax_nopriv_ lack authentication and authorization checks

A user is affected if the WP Bakery Autoresponder Addon plugin is installed and its sensitive functions lack proper capability checks, allowing lower-privileged or unauthenticated users to perform administrator-only actions.

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 checks and nonce verification) on all sensitive endpoints and administrative functions within the plugin. Update to a patched version if available.

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-27362 — 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-27362 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