CVE-2026-6802
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 · uneditedThe Easy Upload Files During Checkout plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 3.0.1. This is due to missing authorization checks in the ufdc_custom_init() function, which processes the 'eufdc-delete' parameter without any nonce verification, capability check, or attachment ownership validation. This makes it possible for unauthenticated attackers to permanently delete arbitrary media library attachments from the WordPress site.
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 confidenceThe Easy Upload Files During Checkout WordPress plugin (versions up to 3.0.1) contains an IDOR vulnerability in the ufdc_custom_init() function. The function processes the 'eufdc-delete' parameter to delete media attachments but lacks three critical security controls: nonce verification, WordPress capability checks, and attachment ownership validation. This allows any unauthenticated user to permanently delete arbitrary files from the site's media library.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check plugin installation and versionNavigate to WordPress admin > Plugins > Installed Plugins, locate 'Easy Upload Files During Checkout', and note the version number displayedAffected if Version is 3.0.1 or earlier
-
Confirm plugin is activeIn the same plugins list, verify the plugin shows as 'Active' under the status columnAffected if Plugin is active and version is 3.0.1 or earlier
-
Locate vulnerable function in sourceAccess the plugin files via FTP or file manager, open the main plugin PHP file (typically easy-upload-files-checkout.php or similar), search for function ufdc_custom_init()Affected if Function ufdc_custom_init() exists and processes $_REQUEST or $_POST parameters
-
Check for nonce verificationWithin ufdc_custom_init(), search for wp_verify_nonce, check_admin_referer, or wp_nonce_verify functions before processing the eufdc-delete parameterAffected if No nonce verification is performed before deleting files
-
Check for capability and ownership validationWithin ufdc_custom_init(), look for current_user_can() checks and ownership validation (such as checking if get_post_field("post_author") matches current user) before allowing deletionAffected if No capability checks and no ownership validation exist before allowing file deletion
User is affected if the plugin version is 3.0.1 or earlier, the plugin is active, and the vulnerable ufdc_custom_init() function processes the eufdc-delete parameter without nonce verification, capability checks, or ownership validation.
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 to version 3.0.2 or later when available. If no patched version exists, disable the plugin and remove it until a secure version is released. Alternatively, the vendor should add wp_verify_nonce(), current_user_can('delete_posts'), and ownership validation before allowing any deletion.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6802 — 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-6802 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