CVE-2024-51645
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 themefusecom ThemeFuse Maintenance Mode themefuse-maintenance-mode allows Stored XSS.This issue affects ThemeFuse Maintenance Mode: from n/a through <= 1.1.3.
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 ThemeFuse Maintenance Mode WordPress plugin allows unauthenticated or low-privileged attackers to trick administrators into submitting malicious requests that inject persistent malicious scripts (Stored XSS) into maintenance mode pages.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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 the plugin is installedCheck for the ThemeFuse Maintenance Mode plugin in the WordPress plugins directory (wp-content/plugins/) or list installed plugins via WordPress admin under Plugins > Installed Plugins.Affected if The ThemeFuse Maintenance Mode plugin appears in the installed plugins list.
-
Identify the installed versionView the plugin details in WordPress admin (Plugins > Installed Plugins > ThemeFuse Maintenance Mode) or inspect the plugin's main PHP file header for the 'Version' comment, typically found in the main plugin file in wp-content/plugins/maintenance-mode-themefuse/ or similar.Affected if The displayed version is older than the patched version released for CVE-2024-51645.
-
Confirm the plugin is activeCheck the WordPress admin plugins page to see if ThemeFuse Maintenance Mode is activated, or query the wp_options table for the active_plugins option.Affected if The plugin status shows as 'Active'.
-
Inspect maintenance mode page content for injected scriptsAccess the plugin settings page (Maintenance Mode > Settings or similar) and examine any fields that accept HTML or scripts (such as custom HTML, header/footer code, or message fields). Also view the source of the live maintenance mode page to check for unexpected script tags.Affected if Any <script> tags, event handlers (onclick, onerror, etc.), or suspicious JavaScript URLs appear in the maintenance mode configuration or rendered page.
A user is affected if the ThemeFuse Maintenance Mode plugin is installed, active, and running a version prior to the CVE-2024-51645 patch, or if unexpected script content is found in the maintenance mode settings.
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 dataUpdate the plugin to the latest patched version; implement anti-CSRF tokens on all state-changing forms and validate/sanitize all user-supplied input before rendering.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51645 — 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-2024-51645 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