dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11571

HIGH · 7.5 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 Everest Forms WordPress plugin before 3.5.0 does not reliably delete temporary CSV files generated during email-notification processing and leaves them publicly accessible in the uploads directory, allowing unauthenticated attackers to retrieve other users' form submission records via predictable, enumerable filenames.

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 Everest Forms WordPress plugin before 3.5.0 fails to reliably delete temporary CSV files generated during email-notification processing. These files containing sensitive form submission data are left in the publicly accessible uploads directory with predictable, enumerable filenames, allowing unauthenticated attackers to retrieve other users' form submission records.

MitigationUpgrade Everest Forms to version 3.5.0 or later to ensure temporary CSV files are properly deleted, and audit the uploads directory for any lingering sensitive files from prior form submissions.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Everest Forms plugin is installed
    Navigate to WordPress admin dashboard > Plugins and confirm Everest Forms appears in the installed plugins list, or inspect the file system at wp-content/plugins/everest-forms/ for the plugin directory.
    Affected if Everest Forms plugin is not installed, this CVE does not apply.
  2. Determine installed Everest Forms version
    In WordPress admin, go to Plugins > Installed Plugins > Everest Forms and note the version number displayed, or open wp-content/plugins/everest-forms/readme.txt and locate the 'Stable tag' entry.
    Affected if The installed version is any version before 3.5.0, making the environment vulnerable.
  3. Locate temporary CSV files in uploads directory
    Browse the WordPress uploads folder (typically wp-content/uploads/) and look for CSV files with temporary or partial filename patterns related to form submissions, such as files prefixed with 'everest-forms-temp-', 'temp_csv_', or similarly predictable naming.
    Affected if Any CSV files exist in the uploads directory that appear to be temporary exports of form submission data.
  4. Verify public accessibility of upload files
    Attempt to access one of the identified CSV files directly via the web browser using the public URL path (for example, https://yoursite.com/wp-content/uploads/filename.csv) without authentication.
    Affected if The CSV file is downloadable without authentication, confirming the files are publicly accessible.

You are affected if Everest Forms version is below 3.5.0 AND temporary CSV files containing form submission data remain in the publicly accessible uploads directory.

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

Upgrade Everest Forms to version 3.5.0 or later to ensure temporary CSV files are properly deleted, and audit the uploads directory for any lingering sensitive files from prior form submissions.

Recommended fix High confidence

Everest Forms 3.5.0 or later

  1. Backup the WordPress site database and files before making any changes
  2. Log in to the WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find Everest Forms in the plugin list and click 'Update now' if an update is available, or manually upload version 3.5.0 or later
  5. Verify the plugin version after update by checking the plugin details page
  6. Check the wp-content/uploads/everest-forms/ directory and delete any遗留的临时CSV文件 (temporary CSV files) that may remain from previous form submissions
  7. Test form submissions to confirm the plugin functions correctly after the update

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

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-11571 — 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-11571 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