CVE-2026-3191
CSRF Vulnerability in Minify HTML WordPress Plugin Allows Settings Manipulation
Publication date: 2026-03-31
Last updated on: 2026-03-31
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_minify | minify_html | to 2.1.12 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Minify HTML plugin for WordPress, in all versions up to and including 2.1.12, is vulnerable to Cross-Site Request Forgery (CSRF). This vulnerability arises because the plugin's 'minify_html_menu_options' function lacks proper nonce validation. As a result, an unauthenticated attacker can trick a site administrator into performing an action, such as clicking a malicious link, which then allows the attacker to update the plugin's settings without authorization.
How can this vulnerability impact me? :
This vulnerability allows an attacker to change the settings of the Minify HTML plugin without proper authorization by exploiting the administrator's session through a forged request. While it does not directly compromise content confidentiality, it can lead to unauthorized modification of plugin behavior, potentially affecting website performance or functionality. The CVSS score of 5.4 indicates a medium severity with impacts on integrity and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the Cross-Site Request Forgery vulnerability in the Minify HTML WordPress plugin, you should update the plugin to version 2.1.13 or later, where the issue has been addressed.
This update includes fixes related to nonce validation in the 'minify_html_menu_options' function, preventing unauthenticated attackers from updating plugin settings via forged requests.
Additionally, ensure that your WordPress installation and all plugins are kept up to date to reduce exposure to known vulnerabilities.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects the Minify HTML WordPress plugin versions up to and including 2.1.12, due to missing or incorrect nonce validation allowing Cross-Site Request Forgery (CSRF). Detection involves identifying if the vulnerable plugin version is installed and if unauthorized changes to plugin settings have occurred.
To detect the vulnerability on your system, first verify the plugin version installed on your WordPress site. You can do this by checking the plugin directory or using WP-CLI commands.
- Check the installed plugin version via WP-CLI: wp plugin status minify-html-markup
- Alternatively, inspect the plugin version in the plugin's main PHP file header or readme.txt file located in wp-content/plugins/minify-html-markup/
To detect potential exploitation attempts on your network, monitor HTTP requests that attempt to update plugin settings without proper authentication or nonce validation. Look for suspicious POST requests targeting the 'minify_html_menu_options' action or similar endpoints.
- Use network monitoring tools or web server logs to filter for POST requests containing 'minify_html_menu_options'. For example, using grep on Apache logs: grep 'minify_html_menu_options' /var/log/apache2/access.log
- Use curl or similar tools to test if the plugin accepts POST requests without valid nonces (only on a test system): curl -X POST -d 'action=minify_html_menu_options&other_params=...' https://yourwordpresssite.com/wp-admin/admin-ajax.php
Note: Since the vulnerability is related to missing nonce validation, detection commands focus on identifying the vulnerable plugin version and monitoring for unauthorized POST requests attempting to change plugin settings.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of the CVE-2026-3191 vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.