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

CVE-2024-54425

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 LionScripts.com LionScripts: Site Maintenance & Noindex Nofollow Plugin maintenance-and-noindex-nofollow allows Stored XSS.This issue affects LionScripts: Site Maintenance & Noindex Nofollow Plugin: from n/a through <= 2.1.

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

A CSRF vulnerability in the LionScripts Site Maintenance & Noindex Nofollow WordPress plugin (versions <= 2.1) allows attackers to forge administrative requests that inject malicious JavaScript (stored XSS) into plugin settings. When other administrators view the affected pages, the injected script executes in their browser context.

MitigationUpdate the plugin to a patched version when available; alternatively, deactivate or remove the plugin until a fix is released. Implement anti-CSRF tokens and input sanitization in plugin admin actions.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'LionScripts Site Maintenance & Noindex Nofollow' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'lionscripts-site-maintenance' or similar.
    Affected if The plugin is not found in the installed plugins list or the plugin folder does not exist in wp-content/plugins/
  2. Check installed version
    In WordPress admin_plugins list, find the LionScripts plugin and note the version number displayed below the plugin name. Compare this to the affected range (versions <= 2.1).
    Affected if The installed version is 2.1 or lower, or if no version is displayed and the plugin appears unupdated.
  3. Confirm plugin is active
    In WordPress admin_plugins, verify the plugin shows as 'Active' (the plugin must be active for the CSRF to be exploitable).
    Affected if The plugin is active and running on the site.
  4. Inspect plugin settings for malicious scripts
    Navigate to the plugin settings page (usually under Settings > Site Maintenance or similar LionScripts menu). View the page source or inspect form values for any unexpected <script> tags, event handlers, or encoded payloads that could indicate stored XSS.
    Affected if Plugin settings contain suspicious JavaScript code, encoded payloads, or unexpected HTML/script tags that were not intentionally added by an administrator.
  5. Review admin action nonces
    Access the plugin PHP files in /wp-content/plugins/ and search for admin action handlers (like admin_post_, wp_ajax_). Check if these handlers verify a nonce or check referer before processing settings updates.
    Affected if Admin actions that update plugin settings lack nonce verification or referer checks, indicating missing CSRF protection.

The environment is affected if the LionScripts Site Maintenance plugin is installed, active, and running version 2.1 or lower, or if plugin settings contain unexpected script injections.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version when available; alternatively, deactivate or remove the plugin until a fix is released. Implement anti-CSRF tokens and input sanitization in plugin admin actions.

Have this fixed 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 help mitigating

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