dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-4347

HIGH · 8.1 CVSS v3.1 Published 2026-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 MW WP Form plugin for WordPress is vulnerable to arbitrary file moving due to insufficient file path validation via the 'generate_user_filepath' function and the 'move_temp_file_to_upload_dir' function in all versions up to, and including, 5.1.0. This makes it possible for unauthenticated attackers to move arbitrary files on the server, which can easily lead to remote code execution when the right file is moved (such as wp-config.php). The vulnerability is only exploitable if a file upload field is added to the form and the “Saving inquiry data in database” option is enabled.

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 MW WP Form WordPress plugin has an arbitrary file move vulnerability due to insufficient path validation in the 'generate_user_filepath' and 'move_temp_file_to_upload_dir' functions. Unauthenticated attackers can move arbitrary files on the server, potentially achieving RCE by moving critical files like wp-config.php, but exploitation requires both a file upload field in the form and the 'Saving inquiry data in database' option to be enabled.

MitigationUpgrade to MW WP Form version 5.1.1 or later; if immediate patching is not possible, disable file upload fields or the database saving feature until the patch can be applied.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MW WP Form plugin is installed
    Check the plugin directory at wp-content/plugins/mw-wp-form/ or query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the active plugins list or the plugin directory exists
  2. Determine the installed plugin version
    Read the main plugin file header at wp-content/plugins/mw-wp-form/mw-wp-form.php for the 'Version' comment, or query: SELECT option_value FROM wp_options WHERE option_name LIKE 'mw_wp_form%version%';
    Affected if The version number is lower than 5.1.1
  3. Identify forms with file upload fields
    Query the WordPress database for form postmeta containing 'mw-wp-form' post type with file upload field configuration: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key LIKE '%mw-wp-form%' AND meta_value LIKE '%filetype:%' OR meta_value LIKE '%upload%';
    Affected if Any form contains a file upload field configuration (typically indicated by 'filetype' or 'upload' meta values in the form settings)
  4. Check if database saving is enabled
    Query the WordPress database for form settings that enable inquiry data storage: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = 'mw-wp-form-data' AND meta_value LIKE '%save%';
    Affected if The 'Saving inquiry data in database' option is enabled in any form configuration (often indicated by 'save' or 'database' in the meta value)

The environment is affected if MW WP Form version is below 5.1.1 AND any form has both a file upload field enabled AND the 'Saving inquiry data in database' option turned on.

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 to MW WP Form version 5.1.1 or later; if immediate patching is not possible, disable file upload fields or the database saving feature until the patch can be applied.

Recommended fix Moderate confidence

MW WP Form version 5.1.1 or higher

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'MW WP Form' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 5.1.1 or higher from the WordPress plugin repository
  5. After updating, verify the version number reflects the patched release
  6. If the vulnerability was present, ensure no unauthorized files (especially wp-config.php) have been modified or moved

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