WPHizmet

Eklenti güvenlik geçmişi

MW WP Form güvenlik açıkları

ABD Ulusal Güvenlik Açığı Veritabanı’nda (NVD) MW WP Form eklentisi için 12 açık kaydı bulunuyor; en yenisi 2 Ekim 2026 tarihli. Bunların 6 tanesi kritik veya yüksek önemde, 9 tanesi oturum açmadan istismar edilebiliyor. Güncel sürüm 5.1.8.

Toplam kayıt
12
Kritik veya yüksek
6
Oturumsuz istismar
9
Son kayıt
2 Ekim 2026

Bilinen açık kayıtları

En yeniden eskiye. Her kaydın özgün metni NVD’de.

  • CVE-2026-96567Yüksek · 7,22 Ekim 2026

    depolanmış siteler arası betik çalıştırma (XSS)

    Etkilenen sürümler: 5.1.7 ve öncesi · Oturum açmadan istismar edilebilir

    The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_id' parameter in all versions up to, and including, 5.1.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The CSRF gate protecting form submission (MW_WP_Form_Csrf) is bypassable by any unauthenticated visitor who first loads the public form page to obtain a valid double-submit cookie, leaving no effective barrier to storing malicious payloads.

    Türkçe kayıt ve ne yapmalı
  • CVE-2026-78363Orta · 4,81 Eylül 2026

    enjeksiyon

    Etkilenen sürümler: 5.1.5 öncesi · Oturum açmadan istismar edilebilir

    The MW WP Form WordPress plugin before 5.1.5 does not prevent shortcodes in user-submitted values from being executed when it merges those values into a message that it later processes for shortcodes, allowing unauthenticated users to run any shortcode registered on the site. Exploitation requires the site to have been configured to echo a submitted value back to the visitor after submission.

  • CVE-2026-78364Düşük · 3,530 Ağustos 2026

    depolanmış siteler arası betik çalıştırma (XSS)

    Etkilenen sürümler: 5.1.6 öncesi

    The MW WP Form WordPress plugin before 5.1.6 does not sanitise and escape some of its form settings before outputting them back in an admin dashboard page, which could allow users with a role as low as Editor to perform Stored Cross-Site Scripting attacks against high privilege users such as admin.

  • CVE-2026-48871Yüksek · 7,116 Haziran 2026

    siteler arası betik çalıştırma (XSS)

    Etkilenen sürümler: 5.1.3 ve öncesi · Oturum açmadan istismar edilebilir

    Unauthenticated Cross Site Scripting (XSS) in MW WP Form <= 5.1.3 versions.

  • CVE-2026-8853Orta · 4,410 Haziran 2026

    depolanmış siteler arası betik çalıştırma (XSS)

    Etkilenen sürümler: 5.1.3 ve öncesi

    The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'memo' parameter in all versions up to, and including, 5.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the memo value is stored via update_post_meta() rather than wp_insert_post(), WordPress's built-in kses and unfiltered_html protections do not apply, allowing attackers to break out of the textarea element via injected closing tags regardless of role-based content filtering.

  • CVE-2026-6206Orta · 5,314 Mayıs 2026

    hassas bilgi ifşası

    Etkilenen sürümler: 5.1.2 ve öncesi · Oturum açmadan istismar edilebilir

    The MW WP Form plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 5.1.2 via the _get_post_property_from_querystring() function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to.

  • CVE-2026-5436Yüksek · 8,19 Nisan 2026

    uzaktan kod çalıştırma

    Etkilenen sürümler: 5.1.1 ve öncesi · Oturum açmadan istismar edilebilir

    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.

  • CVE-2026-4347Yüksek · 8,12 Nisan 2026

    uzaktan kod çalıştırma

    Etkilenen sürümler: 5.1.0 ve öncesi · Oturum açmadan istismar edilebilir

    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.

  • CVE-2023-46206Orta · 5,32 Ocak 2025

    eksik yetki denetimi

    Etkilenen sürümler: 4.4.5 ve öncesi · Oturum açmadan istismar edilebilir

    Missing Authorization vulnerability in Webの相談所 MW WP Form mw-wp-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MW WP Form: from n/a through <= 4.4.5.

  • CVE-2024-24804Orta · 5,410 Şubat 2024

    depolanmış siteler arası betik çalıştırma (XSS)

    Etkilenen sürümler: 5.0.6 ve öncesi

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in websoudan MW WP Form allows Stored XSS.This issue affects MW WP Form: from n/a through 5.0.6.

  • CVE-2023-6316Kritik · 9,811 Ocak 2024

    kısıtlamasız dosya yükleme

    Etkilenen sürümler: 5.0.1 ve öncesi · Oturum açmadan istismar edilebilir

    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.

  • CVE-2023-6559Kritik · 9,816 Aralık 2023

    rastgele dosya silme

    Etkilenen sürümler: 5.0.3 ve öncesi · Oturum açmadan istismar edilebilir

    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.

Kaynak: NVD (kamu malı veri) ve WordPress.org eklenti dizini. Kayıtlar eklentinin WordPress.org adresi veya tam adıyla eşleştirilir. Veri 7 Ekim 2026 itibarıyla.