dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-49055

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in Drag and Drop Multiple File Upload – Contact Form 7 <= 1.3.9.7 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 confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in the WordPress plugin 'Drag and Drop Multiple File Upload – Contact Form 7' affecting versions 1.3.9.7 and below. An unauthenticated attacker can inject malicious JavaScript through the plugin's file upload functionality, which executes in the browsers of users who interact with affected pages.

MitigationUpdate the plugin to a version newer than 1.3.9.7, or remove the plugin if no patched version is available. Ensure all users are logged out and back in after patching to clear any potentially stored malicious payloads.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Check if the plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'Drag and Drop Multiple File Upload - Contact Form 7' in the list
    Affected if the plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the Plugins list, locate the plugin and click on the plugin name to view its details, or look for the version number displayed under the plugin name in the list view
    Affected if the version shown is 1.3.9.7 or any version number lower than 1.3.9.7
  3. Verify the plugin is active
    In the Plugins list, check if the 'Drag and Drop Multiple File Upload - Contact Form 7' shows as 'Active' under the plugin status
    Affected if the plugin is active and the version is 1.3.9.7 or below

You are affected if the plugin 'Drag and Drop Multiple File Upload - Contact Form 7' is installed, active, and running version 1.3.9.7 or lower.

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 the plugin to a version newer than 1.3.9.7, or remove the plugin if no patched version is available. Ensure all users are logged out and back in after patching to clear any potentially stored malicious payloads.

Recommended fix Moderate confidence

Latest version of Drag and Drop Multiple File Upload – Contact Form 7 plugin (version > 1.3.9.7)

  1. Navigate to WordPress admin dashboard > Plugins
  2. Locate 'Drag and Drop Multiple File Upload – Contact Form 7' plugin
  3. Check the current installed version to confirm it is 1.3.9.7 or lower
  4. Update the plugin to the latest available version from the WordPress plugin repository
  5. Verify the update was successful and the new version is above 1.3.9.7

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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