dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14782

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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 – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.49.1 via the 'listen_for_csv_export' function. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with access to the Forminator dashboard, to export sensitive form submission data including personally identifiable information.

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 plugin for WordPress contains an authorization bypass in its listen_for_csv_export function. The vulnerability allows any authenticated user with Forminator dashboard access to export sensitive form submission data, including personally identifiable information, without proper capability checks verifying authorization to access that specific data.

MitigationUpdate the Forminator plugin to version 1.49.2 or later which contains the authorization fix. Until patched, limit dashboard access to only trusted administrators and consider disabling the export functionality if not needed.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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. Confirm Forminator plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate Forminator plugin and note the version number displayed
    Affected if The installed version is lower than 1.49.2 (the fixed release)
  2. Verify Forminator dashboard access exists
    Check WordPress user roles and capabilities to see which users have access to the Forminator plugin admin area (typically Forms > Dashboard in wp-admin)
    Affected if Any user role other than Administrator has Forminator dashboard access
  3. Identify if CSV export functionality is accessible
    Check if the form submission export feature exists by reviewing Forminator settings or attempting to access a form's submissions export option (Forms > select form > Submissions > Export)
    Affected if CSV export functionality is available to users with dashboard access
  4. Locate the vulnerable function
    Inspect the Forminator plugin files, specifically looking for the listen_for_csv_export function in the plugin codebase
    Affected if The function exists and is accessible without additional capability verification beyond basic dashboard access

The environment is affected if Forminator plugin version is below 1.49.2 AND any authenticated user with Forminator dashboard access can export form submission data without role-specific authorization checks.

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 Forminator plugin to version 1.49.2 or later which contains the authorization fix. Until patched, limit dashboard access to only trusted administrators and consider disabling the export functionality if not needed.

Recommended fix Moderate confidence

Forminator Forms plugin version 1.49.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Forminator Forms plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is 1.49.2 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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