dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3642

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-15
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
The e-shot™ form builder plugin for WordPress is vulnerable to Missing Authorization in all versions up to and including 1.0.2. The eshot_form_builder_update_field_data() AJAX handler lacks any capability checks (current_user_can()) or nonce verification (check_ajax_referer()/wp_verify_nonce()). The function is registered via the wp_ajax_ hook, making it accessible to any authenticated user. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify form field configurations including mandatory status, field visibility, and form display preferences via the eshot_form_builder_update_field_data AJAX action.

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 e-shot™ form builder plugin for WordPress is vulnerable to missing authorization in the eshot_form_builder_update_field_data() AJAX handler. This function lacks both capability checks (current_user_can()) and nonce verification (check_ajax_referer()), making it accessible to any authenticated user with Subscriber-level access or higher. Attackers can modify form field configurations including mandatory status, field visibility, and form display preferences.

MitigationAdd proper capability checks (e.g., current_user_can('manage_options')) and nonce verification to the eshot_form_builder_update_field_data AJAX handler to ensure only authorized users can modify form configurations.

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 e-shot form builder plugin is installed
    Navigate to WordPress admin > Plugins and look for 'e-shot form builder' or 'eshot' in the plugin list, or check the wp-content/plugins directory for a folder containing 'eshot' or 'e-shot'.
    Affected if The e-shot form builder plugin is installed and active.
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find the e-shot form builder entry and note the version number displayed. Compare this to the vendor's release notes for any version that addressed authorization issues.
    Affected if The installed version has not received a security update addressing the missing authorization flaw.
  3. Confirm AJAX handler exists in the plugin
    Examine the plugin's PHP files for the function 'eshot_form_builder_update_field_data' hooked via 'wp_ajax_eshot_form_builder_update_field_data' or 'wp_ajax_nopriv_eshot_form_builder_update_field_data'.
    Affected if The AJAX handler 'eshot_form_builder_update_field_data' is registered without capability checks.
  4. Inspect AJAX handler for authorization code
    Open the PHP file containing eshot_form_builder_update_field_data and search for 'current_user_can' or 'manage_options' calls near the function start, and for 'check_ajax_referer' or 'wp_verify_nonce' calls.
    Affected if No capability check (current_user_can) and no nonce verification (check_ajax_referer) are present in the handler.
  5. Verify subscriber-level users exist
    In WordPress admin > Users, check if any users have the 'Subscriber' role assigned. Any such user can exploit this vulnerability.
    Affected if At least one user with Subscriber-level access exists in the WordPress installation.

If the e-shot form builder plugin is active, the eshot_form_builder_update_field_data AJAX handler lacks capability and nonce checks, and any Subscriber-level user exists, the environment is affected by this authorization bypass.

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

Add proper capability checks (e.g., current_user_can('manage_options')) and nonce verification to the eshot_form_builder_update_field_data AJAX handler to ensure only authorized users can modify form configurations.

Recommended fix Moderate confidence

Version 1.0.3 or later (next release after 1.0.2)

  1. Update the e-shot™ form builder plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify the eshot_form_builder_update_field_data() AJAX handler now includes capability checks (current_user_can()) and nonce verification
  3. Confirm that users with Subscriber-level access can no longer access the AJAX action without proper permissions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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