CVE-2026-40769
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 Arbitrary File Deletion in Contact Form Extender for Divi – Save Entries, File Upload & Country Code Field <= 1.0.6 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 · high confidenceAn unauthenticated arbitrary file deletion vulnerability exists in the Contact Form Extender for Divi WordPress plugin (Save Entries, File Upload & Country Code Field) versions 1.0.6 and earlier. Attackers can delete arbitrary files on the server without any authentication, potentially leading to site compromise or denial of service by removing critical files.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
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.
-
Verify the plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Contact Form Extender for Divi' in the list of installed plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status
-
Check the plugin versionIn the Plugins list, click on the plugin name or view its details to see the installed version number. Alternatively, inspect the plugin's main PHP file header for the 'Version' tag.Affected if The reported version is 1.0.6 or below (e.g., 1.0.5, 1.0.4, 1.0.3, etc.)
-
Confirm the plugin is activeIn the WordPress Plugins list, check if 'Contact Form Extender for Divi' shows as 'Active' under the status column.Affected if The plugin is active on the site
-
Verify file deletion capability exposureReview the plugin's publicly accessible endpoints (check plugin directory for AJAX handlers or public functions handling file operations). The vulnerability allows unauthenticated file deletion, so any exposed file deletion function is a concern.Affected if The plugin exposes any file deletion functionality that can be accessed without authentication
The environment is affected if the Contact Form Extender for Divi plugin is installed with version 1.0.6 or below and is active on the WordPress site, allowing unauthenticated attackers to delete arbitrary files.
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.
From vendor dataUpdate the Contact Form Extender for Divi plugin to version 1.0.7 or later. If an update is unavailable, consider removing the plugin until a patch is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40769 — 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-40769 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