dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14067

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-14
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 Easy Form Builder plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on multiple AJAX actions in all versions up to, and including, 3.9.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive form response data, including messages, admin replies, and user information due to a logic error in the authorization check that uses AND (&&) instead of OR (||).

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 Form Builder WordPress plugin has a broken access control vulnerability caused by a logic error where the authorization check uses AND (&&) instead of OR (||). This forces both conditions to be true simultaneously, inadvertently allowing authenticated users with Subscriber-level access (the lowest privilege) to bypass intended restrictions and access sensitive form response data including user submissions, admin replies, and personal information.

MitigationUpdate the Easy Form Builder plugin to version 3.9.4 or later, which corrects the authorization logic. Verify all form functionality and access controls post-update.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Easy Form Builder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Form Builder' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active in WordPress
  2. Check installed plugin version
    On the Plugins page, find Easy Form Builder and locate the version number displayed below the plugin name. Compare this version to 3.9.4.
    Affected if Version is below 3.9.4 (e.g., 3.9.3, 3.9.2, etc.)
  3. Identify Subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the Role column. Count or note any users assigned the 'Subscriber' role.
    Affected if At least one user with Subscriber role exists on the site
  4. Test access to form response data
    Log in as a Subscriber-level user. Navigate to any Easy Form Builder form submission page or endpoint that should normally require higher privileges (e.g., view other users submissions, admin replies, or sensitive response data). Attempt to access or download this data.
    Affected if Subscriber-level users can view, access, or download form responses, admin replies, or personal information they should not have access to
  5. Review plugin authorization logic
    If you have file access, examine the Easy Form Builder plugin file that handles permission checks (typically in includes/ or classes/ directories). Look for authorization code containing && operators where || was likely intended for role-based access control.
    Affected if The authorization code uses && (AND) logic requiring both conditions simultaneously instead of || (OR) logic, allowing lower-privileged users to pass checks meant for higher roles

You are affected if the Easy Form Builder plugin is installed at a version below 3.9.4 and Subscriber-level users can access sensitive form response data that should be restricted to higher-privileged roles.

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 Form Builder plugin to version 3.9.4 or later, which corrects the authorization logic. Verify all form functionality and access controls post-update.

Recommended fix Moderate confidence

Latest version after 3.9.3 (check WordPress Plugin Repository for 3.9.4 or later)

  1. Check for plugin updates in WordPress admin dashboard under Plugins > All Plugins
  2. Update Easy Form Builder plugin to the latest available version
  3. If no update is available, verify the current version in Plugins > All Plugins and confirm the exact fixed version from the plugin's changelog or the WordPress Plugin Repository
  4. After updating, verify the fix by confirming the AJAX actions now properly check for authorization using OR (||) logic rather than AND (&&)

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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