CVE-2026-57750
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 · uneditedUnauthenticated Broken Access Control in ez Form Calculator Premium <= 2.14.1.2 versions.
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 confidenceUnauthenticated Broken Access Control in ez Form Calculator Premium WordPress plugin versions 2.14.1.2 and below allows attackers to access privileged functionality or data without proper authentication. The vulnerability has a CVSS 5.3 medium severity rating, indicating the potential for unauthorized access to sensitive operations or information.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the ez Form Calculator Premium plugin installationCheck for the plugin directory at wp-content/plugins/ez-form-calculator-premium/ or similar path in your WordPress installationAffected if The plugin directory exists on the server
-
Identify the installed plugin versionOpen the main plugin file (usually ez-form-calculator-premium.php) and locate the version comment/constant, or view the plugin in WordPress admin under Plugins > Installed PluginsAffected if The version displayed is 2.14.1.2 or lower
-
Confirm the plugin is activeCheck the WordPress admin under Plugins > Installed Plugins to see if ez Form Calculator Premium is activatedAffected if The plugin shows as Active and meets the version condition above
Your environment is affected if ez Form Calculator Premium plugin is installed, active, and running version 2.14.1.2 or below, exposing unauthenticated access to privileged functions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate ez Form Calculator Premium to the latest version beyond 2.14.1.2. If no patch is available, implement web application firewall rules or additional authentication controls to restrict access to the plugin's administrative functions.
Latest version of ez Form Calculator Premium (verify > 2.14.1.2 on plugin repository or vendor site)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate ez Form Calculator Premium
- 4. Check the current installed version number
- 5. If the current version is 2.14.1.2 or lower, update the plugin to the latest available version
- 6. Verify the update was successful and test form calculator functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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