Drag And Drop Multiple File Upload Contact Form 7WordPress extension · Codedropz
CVE-2022-45364
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Glen Don L. Mongaya Drag and Drop Multiple File Upload – Contact Form 7 plugin <= 1.3.6.5 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Drag and Drop Multiple File Upload – Contact Form 7 WordPress plugin versions 1.3.6.5 and below allows attackers to trick authenticated users into submitting unintended requests, potentially leading to malicious file uploads or form submissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Drag And Drop Multiple File Upload Contact Form 7WordPress extension
<= 1.3.6.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Codedropz Drag And Drop Multiple File Upload' or check the /wp-content/plugins/ directory for a folder containing 'codedropz' or 'drag-drop' in the nameAffected if The plugin is present in the WordPress installation
-
Determine the installed versionIn the WordPress admin > Plugins list, find the plugin and read the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually in the plugin root folder) and look for the 'Version' header in the plugin comment blockAffected if Version is 1.3.6.5 or lower (any version up to and including 1.3.6.5)
-
Check form submission handlers for nonce validationExamine the main plugin PHP files for form handling functions. Search for presence of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' calls within functions that process form submissions or file uploads. If these calls are missing, the plugin lacks CSRF protectionAffected if Form submission handlers do not verify nonce tokens before processing requests
-
Verify AJAX action handlers have nonce checksLook for AJAX action callbacks (registered via 'add_action("wp_ajax_..."' or 'add_action("wp_ajax_nopriv_..."') in the plugin code. Check if these handlers include nonce verification using wp_verify_nonce or check_ajax_referer. Missing checks indicate vulnerabilityAffected if AJAX handlers that process file uploads or form data do not validate nonce tokens
You are affected if the Codedropz Drag And Drop Multiple File Upload plugin is installed at version 1.3.6.5 or lower AND the code handling form submissions or AJAX actions lacks proper nonce validation (wp_verify_nonce, check_ajax_referer, or check_admin_referer calls).
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 plugin to a patched version above 1.3.6.5 that implements proper anti-CSRF token validation and nonce checks on all form submissions and AJAX actions.
Fix this in Drag And Drop Multiple File Upload Contact Form 7
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45364 — 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-2022-45364 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