dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-3191

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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
The Minify HTML plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.12. This is due to missing or incorrect nonce validation on the 'minify_html_menu_options' function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Minify HTML WordPress plugin versions up to 2.1.12 lack proper nonce validation in the 'minify_html_menu_options' function, allowing unauthenticated attackers to forge requests that modify plugin settings. This CSRF vulnerability requires social engineering to trick an administrator into clicking a malicious link while authenticated.

MitigationUpdate the plugin to version 2.1.13 or later which includes proper nonce validation, or add wp_nonce_field() verification to the affected function.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Confirm Minify HTML plugin is installed
    Go to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Minify HTML' or 'minify-html'. Note whether the plugin is active.
    Affected if The Minify HTML plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In the Plugins list, click on the Minify HTML plugin to view its details, or check the plugin's main PHP file header for the 'Version' comment. Compare this to the version noted as fixed in the CVE advisory.
    Affected if The installed version is older than the fixed version released for CVE-2026-3191
  3. Inspect the nonce validation in the affected function
    Access the plugin source files via FTP or file manager. Locate the 'minify_html_menu_options' function (typically in the main plugin file). Check if the function includes wp_verify_nonce or check_admin_referer before processing settings changes.
    Affected if The function lacks proper WordPress nonce verification (wp_verify_nonce or check_admin_referer) before processing administrative options
  4. Review admin logs for forged requests
    Check WordPress activity logs, server access logs, or security plugins for any unexpected settings changes to the Minify HTML plugin, especially from unexpected IP addresses or referrers.
    Affected if There are settings modifications to the Minify HTML plugin that were not initiated by legitimate administrator actions
  5. Verify admin session integrity
    Check if any admin accounts have active sessions from unknown locations or if there are signs of compromised admin credentials in the user management area.
    Affected if Admin accounts show suspicious session activity or unauthorized access patterns

A site is affected if the Minify HTML plugin is installed, the installed version is older than the fixed version, and the minify_html_menu_options function lacks proper nonce verification.

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 version 2.1.13 or later which includes proper nonce validation, or add wp_nonce_field() verification to the affected function.

Recommended fix High confidence

Minify HTML version 2.1.13 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Minify HTML' plugin
  4. Check if current version is 2.1.12 or lower
  5. If vulnerable, click 'Update Now' to upgrade to latest version
  6. Alternatively, upload Minify HTML version 2.1.13 or later manually
  7. After update, verify the plugin version in Plugins list
  8. Review plugin settings in Settings > Minify HTML to confirm settings are intended

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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