dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-12579

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Regular Expression Denial of Service (ReDoS) in all versions up to, and including, 2.1.10. This is due to processing user-supplied input as a regular expression. This makes it possible for unauthenticated attackers to create comments that can cause catastrophic backtracking and break pages.

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 plugin for WordPress versions up to 2.1.10 is vulnerable to Regular Expression Denial of Service (ReDoS). The plugin processes user-supplied input (specifically comment content) as a regular expression without proper sanitization, allowing unauthenticated attackers to craft inputs that cause catastrophic backtracking and render pages unresponsive or broken.

MitigationUpdate the Minify HTML plugin to the latest patched version. Until patched, consider disabling the plugin or implementing a Web Application Firewall (WAF) rule to filter malicious regex patterns in comment submissions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 Minify HTML plugin version
    Navigate to WordPress Admin > Plugins > Installed Plugins, locate 'Minify HTML' and read the version number from the plugin description. Alternatively, inspect the main plugin file (minify-html.php) in wp-content/plugins/ and look for the 'Version:' header comment.
    Affected if Version is 2.1.10 or lower (any version up to and including 2.1.10)
  2. Confirm plugin is active
    In WordPress Admin > Plugins, verify that Minify HTML shows as 'Active' under the plugin status.
    Affected if Plugin is currently activated on the WordPress site
  3. Verify comment functionality is enabled
    Go to WordPress Admin > Settings > Discussion and check the option 'Allow people to submit comments on new posts'. This setting controls whether comment submissions are processed.
    Affected if Comment posting is enabled in WordPress discussion settings

You are affected if Minify HTML plugin version 2.1.10 or earlier is active on your WordPress site and comment submission is enabled, allowing unauthenticated attackers to submit crafted comment content that triggers catastrophic regex backtracking.

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 Minify HTML plugin to the latest patched version. Until patched, consider disabling the plugin or implementing a Web Application Firewall (WAF) rule to filter malicious regex patterns in comment submissions.

Recommended fix Moderate confidence

Upgrade to the latest version of Minify HTML plugin (version higher than 2.1.10)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Minify HTML' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update completed successfully

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-2024-12579 — 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-2024-12579 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