CVE-2026-24384
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in launchinteractive Merge + Minify + Refresh merge-minify-refresh allows Cross Site Request Forgery.This issue affects Merge + Minify + Refresh: from n/a through <= 2.14.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Merge + Minify + Refresh WordPress plugin (versions through 2.14) allows attackers to induce authenticated administrators to perform unintended actions such as triggering cache clears or configuration changes via maliciously crafted requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Merge + Minify + Refresh plugin is installedNavigate to WordPress admin > Plugins and confirm Merge + Minify + Refresh appears in the installed plugins listAffected if The plugin is present in the WordPress installation
-
Identify installed plugin versionIn Plugins list, click the plugin name or view the plugin files to read the version number from the plugin header in the main PHP file (typically merge-minify-refresh.php)Affected if The installed version is 2.14 or lower (any version through 2.14)
-
Inspect AJAX action handlers for nonce validationExamine the plugin PHP files for action hooks handling cache clears or settings changes. Search for 'add_action' calls for wp_ajax_ and verify each handler calls 'check_ajax_referer' or 'wp_verify_nonce' before processingAffected if AJAX endpoints that modify settings or clear cache lack nonce verification calls
-
Check form submissions for CSRF protectionReview plugin PHP files that handle form POST requests (for settings pages, cache operations). Look for presence of 'wp_nonce_field' in forms and 'wp_verify_nonce' or 'check_admin_referer' in the handling codeAffected if Forms that trigger configuration changes or cache operations do not include or validate nonce tokens
-
Verify request origin validationSearch plugin code for $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] checks that validate the request originates from trusted sourcesAffected if No Origin or Referer header validation exists on state-changing endpoints
The environment is affected if the Merge + Minify + Refresh plugin is installed at version 2.14 or lower and the plugin lacks nonce validation on its AJAX actions or form handlers that perform cache clears or configuration changes.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement anti-CSRF tokens (nonces) on all state-changing operations (forms, AJAX endpoints) and validate Origin/Referer headers to ensure requests originate from trusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-24384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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