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

CVE-2024-54410

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 eagerterrier SOPA Blackout sopa-blackout allows Stored XSS.This issue affects SOPA Blackout: from n/a through <= 1.4.

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

CSRF vulnerability in the SOPA Blackout WordPress plugin (versions <= 1.4) allows authenticated or unauthenticated attackers to inject malicious JavaScript via forged requests, resulting in stored XSS. The plugin lacks proper CSRF token validation on form submissions, enabling attackers to craft requests that execute arbitrary scripts in users' browsers.

MitigationUpdate to the latest version of SOPA Blackout when a patch is released. In the interim, disable the plugin if not essential, and implement additional CSRF protections (nonce tokens) on any admin actions if the plugin is used.

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 SOPA Blackout plugin is installed
    Check your WordPress installation under wp-content/plugins/ for a folder named 'sopa-blackout' or 'sopa-blackout-plugin', or look for the plugin in the WordPress admin under Plugins > Installed Plugins
    Affected if The SOPA Blackout plugin folder exists in your plugins directory
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find SOPA Blackout; the version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The reported version is 1.4 or lower (e.g., 1.4, 1.3, 1.2, 1.1, 1.0)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify whether SOPA Blackout shows as 'Active' under the plugin status
    Affected if The plugin is currently activated and version is 1.4 or lower

You are affected if the SOPA Blackout plugin is installed, active, and running version 1.4 or lower, as this version lacks CSRF protection on form submissions allowing stored XSS.

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 to the latest version of SOPA Blackout when a patch is released. In the interim, disable the plugin if not essential, and implement additional CSRF protections (nonce tokens) on any admin actions if the plugin is used.

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-54410 — 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-54410 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