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

CVE-2024-54405

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 etemplates ECT Social Share ect-social-share allows Stored XSS.This issue affects ECT Social Share: from n/a through <= 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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the ECT Social Share plugin allows attackers to craft malicious requests that inject and store XSS payloads. Successful exploitation enables arbitrary script execution in victims' browsers when they view content containing the injected malicious code.

MitigationImplement CSRF token validation on all form submissions and state-changing operations; apply strict input sanitization and output encoding for all user-supplied data before storage and rendering.

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. Identify if ECT Social Share plugin is installed
    Check your CMS plugin directory for the ECT Social Share plugin folder. In WordPress, this would typically be in wp-content/plugins/. Look for a folder named 'ect-social-share', 'ect-social-share-pro', or similar.
    Affected if The plugin is installed and active in the environment
  2. Determine installed version of ECT Social Share
    Locate the main plugin file (usually index.php or main PHP file in the plugin folder) and check the plugin header for the Version field. Alternatively, access the plugin management interface in your CMS admin panel to view installed plugin versions.
    Affected if Any version of the ECT Social Share plugin is installed (no version range provided for comparison)
  3. Inspect form submissions for CSRF token presence
    Examine the plugin's form handling code (PHP files in the plugin folder) for state-changing operations such as settings saves, content submissions, or social share configuration updates. Look for nonce verification or CSRF token validation functions like wp_verify_nonce, check_ajax_referer, or similar CSRF protection mechanisms.
    Affected if Forms and state-changing operations lack CSRF token validation (vulnerable to CVE-2024-54405)
  4. Check stored content for injected XSS payloads
    Review the database tables where the plugin stores social share content, buttons, or custom messages. Query the relevant tables (often named with 'ect', 'social', 'share' prefixes) for suspicious JavaScript tags, script elements, or event handlers in stored data fields.
    Affected if Stored content contains unsanitized JavaScript or HTML (evidence of exploitation)
  5. Review server access logs for CSRF attack patterns
    Search web server logs (Apache, Nginx, or CMS-specific logs) for POST requests to the plugin's admin-ajax.php, settings pages, or form handlers that lack proper referer validation or originate from external sources attempting to modify plugin settings.
    Affected if Logs show unauthorized POST requests to plugin endpoints without valid CSRF tokens

A user is affected if the ECT Social Share plugin is installed and its forms/settings endpoints lack CSRF token validation, allowing stored XSS injection.

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

Implement CSRF token validation on all form submissions and state-changing operations; apply strict input sanitization and output encoding for all user-supplied data before storage and rendering.

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