dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0825

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-28
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 Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the CSV export functionality in all versions up to, and including, 1.4.5. This makes it possible for unauthenticated attackers to download sensitive form submission data containing personally identifiable information (PII) by accessing the CSV export endpoint with an export key that is exposed in publicly accessible page source code. The vulnerability is created because while the shortcode properly filters displayed entries by user, the CSV export handler completely bypasses this filtering and exports all entries regardless of user permissions.

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 WordPress form database plugin fails to enforce authorization checks on its CSV export endpoint. While the shortcode for displaying form entries properly filters data by user permissions, the CSV export handler completely bypasses this filtering and exports all entries. Attackers can obtain the export key from page source code and download sensitive PII without any authentication.

MitigationUpdate to version 1.4.6 or later which includes proper capability checks on the CSV export function; alternatively, disable CSV export functionality until a patch is available.

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. Identify the WordPress form database plugin
    Check the WordPress plugins directory or wp-content/plugins folder for a form database plugin. Look for directories with names like 'form-database', 'wp-form-db', or similar. Also check wp-admin > Plugins for an installed form database plugin.
    Affected if No form database plugin is found, then this CVE does not apply.
  2. Determine the installed plugin version
    In wp-admin > Plugins, find the form database plugin and note the version number displayed. Alternatively, read the main plugin PHP file header which contains the Version field.
    Affected if The installed version is any version prior to 1.4.6 (e.g., 1.4.5, 1.4.0, 1.3.x). Versions 1.4.6 and later are not affected.
  3. Check if CSV export functionality is enabled
    Look for a CSV export feature in the plugin settings or check if a CSV export shortcode attribute exists. Inspect the plugin admin panel for export options under form settings.
    Affected if CSV export is enabled or available in the plugin configuration.
  4. Inspect page source for exposed export keys
    View the HTML source of any page containing a form database shortcode. Search for strings like 'export', 'csv', 'key', or 'export_key' in the page source.
    Affected if An export key or export URL is visible in the page source code without authentication requirements.

You are affected if the form database plugin is installed with a version before 1.4.6 and the CSV export functionality is accessible with an exposed export key in the page source.

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 to version 1.4.6 or later which includes proper capability checks on the CSV export function; alternatively, disable CSV export functionality until a patch is available.

Recommended fix Moderate confidence

Version 1.4.6 or later (the first version after 1.4.5 that addresses the missing authorization vulnerability)

  1. 1. Update the 'Database for Contact Form 7, WPforms, Elementor forms' WordPress plugin to the latest available version from the WordPress plugin repository.
  2. 2. After updating, verify that the CSV export functionality now properly checks user capabilities before allowing exports.
  3. 3. If immediate update is not possible, disable or restrict access to any publicly accessible CSV export endpoints via web server configuration (e.g., .htaccess rules) or firewall rules.
  4. 4. Review recent form submission logs for any unauthorized CSV export attempts.
  5. 5. Consider resetting any exposed export keys and implementing proper access controls.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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