dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67577

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-09
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 hassantafreshi Easy Form Builder easy-form-builder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Easy Form Builder: from n/a through <= 3.8.20.

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 the WordPress Easy Form Builder plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before granting access to certain functionality, potentially allowing unauthorized users to perform actions they should not have permission to perform.

MitigationUpdate Easy Form Builder to the latest version which should include proper authorization checks. If no update is available, restrict access to the plugin's admin functions via server-side access controls or disable the plugin 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
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 Easy Form Builder plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Easy Form Builder' in the list of active plugins.
    Affected if The plugin appears in the list of installed plugins, regardless of activation status.
  2. Identify installed plugin version
    In the plugins list, click on 'Easy Form Builder' details or open the main plugin file (usually easy-form-builder.php) and locate the 'Version:' header comment to read the version number.
    Affected if Any version of Easy Form Builder is installed. Since no fixed vulnerable version range is provided, compare your version to the latest available version on the WordPress plugin repository - if your version is older than the current release, it may be vulnerable.
  3. Check for unauthorized admin access patterns
    Review WordPress user roles and capabilities. Go to Users > All Users and examine if any users with Subscriber, Contributor, or Author roles have access to Form Builder settings, submissions, or export functionality they should not access. Also check Users > Roles if a role called 'Form Builder' or similar elevated access exists unexpectedly.
    Affected if Users with low-privilege roles (Subscriber, Contributor, Author) can access Form Builder administrative functions, submissions, or export features that should require Editor or Administrator privileges.
  4. Audit plugin capability settings
    Navigate to the Easy Form Builder settings page (usually under Forms or Settings in admin menu). Check the 'Security Level' or 'Access Control' configuration. Look for any setting that allows 'All Users' or low-privilege roles to create, edit, view, or export forms.
    Affected if The plugin security/access level is configured to allow unauthenticated or low-privilege users to access forms, submissions, or administrative features.
  5. Inspect server access logs for anomalous plugin usage
    Review web server access logs (Apache/Nginx) for requests to /wp-admin/admin-ajax.php?action=efb_ or /?post_type=efb forms that originate from IP addresses belonging to non-admin users, or look for repeated POST requests to form submission endpoints without proper authentication headers.
    Affected if Non-administrator users are successfully accessing plugin AJAX endpoints or form management pages.

A defender is affected if Easy Form Builder plugin is installed AND the version is older than the latest release AND low-privilege users can access plugin functions they should not be able to reach.

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

Update Easy Form Builder to the latest version which should include proper authorization checks. If no update is available, restrict access to the plugin's admin functions via server-side access controls or disable the plugin until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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