dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6214

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Forminator Forms plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.53.0. This is due to the listen_for_saving_export_schedule() function in library/class-export.php failing to perform a capability check before saving the scheduled export configuration, unlike the parallel listen_for_csv_export() function which correctly verifies user permissions. This makes it possible for authenticated attackers with subscriber-level access to configure a scheduled export job that emails all form submissions to an attacker-controlled email address, resulting in sensitive data exfiltration.

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 Forminator Forms WordPress plugin versions up to 1.53.0 have a missing authorization vulnerability in the listen_for_saving_export_schedule() function within library/class-export.php. This function lacks a capability check that exists in the parallel listen_for_csv_export() function, allowing any authenticated user with subscriber-level access to configure scheduled export jobs that email form submissions to arbitrary email addresses.

MitigationUpdate Forminator Forms to version 1.53.1 or later which implements proper authorization checks. Until the patch is applied, consider restricting the subscriber role or monitoring for unauthorized export 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Check Forminator plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate Forminator Forms. Compare the version number against 1.53.0. Any version up to and including 1.53.0 is affected.
    Affected if The installed version is 1.53.0 or earlier (versions 1.53.1 and later contain the fix)
  2. Verify the vulnerable function exists
    If you have file access, locate the file library/class-export.php within the Forminator plugin directory. Search for the function named listen_for_saving_export_schedule. Confirm it exists in the codebase.
    Affected if The function listen_for_saving_export_schedule() exists without a capability check (compare to listen_for_csv_export() which should have proper authorization)
  3. Review export schedule configurations
    In WordPress admin, navigate to Forminator > Settings > Exports (or similar export settings area). Examine any configured scheduled export jobs. Look for email destinations and their associated forms.
    Affected if Any scheduled export jobs exist that were created by users without administrator-level permissions
  4. Audit user accounts with subscriber role
    In WordPress admin, go to Users and review accounts with the Subscriber role. Check if any subscriber-level accounts were created recently or have unusual activity.
    Affected if Subscriber accounts exist and the Forminator plugin is installed at a vulnerable version
  5. Check for unexpected export email recipients
    Review all Forminator form export settings (accessible via each form's settings). Look for any email addresses in export configurations that are not expected organizational addresses.
    Affected if Export configurations contain email addresses that are not from your organization or were not set by administrators

You are affected if Forminator Forms plugin version is 1.53.0 or earlier AND any subscriber-level user account exists on the WordPress site, as these users could have configured unauthorized scheduled exports.

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 Forminator Forms to version 1.53.1 or later which implements proper authorization checks. Until the patch is applied, consider restricting the subscriber role or monitoring for unauthorized export configurations.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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