Mw Wp Form
Approved changes feed: RSS · Atom
cpe:2.3:a:inc2734:mw_wp_form:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Inc2734 (f54a108b-b9d4-5dc6-b196-a28f927026d2) |
|---|---|
| Product | Mw Wp Form (5467787f-6e7f-5a94-91c9-211bba323d34) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-5436 |
vulnerable | 2026-06-08 08:07:03.703506 |
MW WP Form <= 5.1.1 - Unauthenticated Arbitrary File Move via regenerate_upload_file_keys
HIGH (8.1)
The MW WP Form plugin for WordPress is vulnerable to Arbitrary File Move/Read in all versions up to and including 5.1.1. This is due to insufficient validation of the $name parameter (upload field key) passed to the generate_user_file_dirpath() function, which uses WordPress's path_join() — a function that returns absolute paths unchanged, discarding the intended base directory. The attacker-controlled key is injected via the mwf_upload_files[] POST parameter, which is loaded into the plugin's Data model via _set_request_valiables(). During form processing, regenerate_upload_file_keys() iterates over these keys and calls generate_user_filepath() with the attacker-supplied key as the $name argument — the key survives validation because the targeted file (e.g., wp-config.php) genuinely exists at the absolute path. The _get_attachments() method then re-reads the same surviving keys and passes the resolved file path to move_temp_file_to_upload_dir(), which calls rename() to move the file into the uploads folder. 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.
Published: 2026-04-08T20:25:10.473Z
Updated: 2026-04-10T20:50:10.628Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-4347 |
vulnerable | 2026-06-08 08:05:13.263556 |
MW WP Form <= 5.1.0 - Unauthenticated Arbitrary File Move via move_temp_file_to_upload_dir
HIGH (8.1)
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.
Published: 2026-04-02T05:28:07.910Z
Updated: 2026-04-08T16:37:50.152Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6559 |
vulnerable | 2026-06-08 06:21:54.861418 |
MW WP Form <= 5.0.3 - Improper Limitation of File Name to Unauthenticated Arbitrary File Deletion
HIGH (7.5)
The MW WP Form plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 5.0.3. This is due to the plugin not properly validating the path of an uploaded file prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible.
Published: 2023-12-16T12:29:16.960Z
Updated: 2026-04-08T16:48:36.983Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6316 |
vulnerable | 2026-06-08 06:19:46.915274 |
MW WP Form <= 5.0.1 - Unauthenticated Arbitrary File Upload
CRITICAL (9.8)
The MW WP Form plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the '_single_file_upload' function in versions up to, and including, 5.0.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Published: 2024-01-11T08:32:51.833Z
Updated: 2026-04-08T17:16:30.886Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.