dbcve.org
Minify HtmlWordPress extension · Dogblocker

CVE-2023-26014

HIGH · 8.8 CVSS v3.1 Published 2023-05-23
Fix available
A fix is available. Upgrade to after 2.1.7 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in Tim Eckel Minify HTML plugin <= 2.1.7 vulnerability.

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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Minify HTML plugin by Tim Eckel (versions 2.1.7 and below). The plugin fails to properly validate anti-CSRF tokens, allowing attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or injecting malicious content through the minification process.

MitigationImplement anti-CSRF tokens (WordPress nonces) on all form submissions and AJAX actions within the plugin, and verify the nonce validity server-side before processing any state-changing requests. Ensure users are running the latest patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Minify HtmlWordPress extension
Affected:<= 2.1.7

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check if Minify HTML plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Minify HTML' or 'Dogblocker Minify Html' by Tim Eckel in the installed plugins list
    Affected if The plugin is present in the plugins directory regardless of activation status
  2. Identify the installed version
    In WordPress admin > Plugins, find the Minify HTML plugin and locate the version number displayed under the plugin name
    Affected if Version number is 2.1.7 or lower, indicating the vulnerable version range
  3. Confirm plugin is active
    Check if the Minify HTML plugin shows as 'Active' in the Plugins admin page
    Affected if Plugin is currently active, making the CSRF attack surface accessible
  4. Inspect plugin code for nonce implementation
    Access plugin files via FTP or file manager, locate the main plugin PHP file (typically minify-html.php or similar) and search for 'wp_nonce_field', 'wp_create_nonce', 'verify_nonce', or 'check_admin_referer' function calls
    Affected if No anti-CSRF nonce functions are found in the plugin code, indicating the vulnerability is present
  5. Check form submissions for nonce fields
    Examine plugin settings page HTML source for nonce fields in any forms (look for input elements with name containing 'nonce' or '_wpnonce')
    Affected if Forms in the plugin settings page lack nonce input fields, allowing CSRF attacks

You are affected if the Minify HTML plugin (Dogblocker Minify Html) versions 2.1.7 or below is installed and active, and the plugin code lacks proper WordPress nonce validation on state-changing form submissions.

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
Upgrade available Upgrade to a release after 2.1.7
Interim mitigation

Implement anti-CSRF tokens (WordPress nonces) on all form submissions and AJAX actions within the plugin, and verify the nonce validity server-side before processing any state-changing requests. Ensure users are running the latest patched version if available.

Recommended fix Moderate confidence

Update to the latest version of Minify HTML plugin (version higher than 2.1.7)

  1. 1. Check your current Minify HTML plugin version in your WordPress installation
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the Minify HTML plugin by Tim Eckel
  4. 4. If your version is 2.1.7 or lower, update the plugin to the latest available version
  5. 5. After updating, verify the plugin is functioning correctly on your site

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

Fix this in Minify Html Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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