Security readout for executives and security teams
Plain-English summary
CVE-2024-54405 affects the WordPress ECT Social Share plugin through version 1.3. A remote attacker could use CSRF to cause a victim’s browser to store malicious script in the site, creating stored XSS risk. This can affect site integrity, user trust, and potentially exposed visitor or administrator browser context.
Executive priority
Treat as a high-priority website exposure for any WordPress property using this plugin. The main business concern is persistent script injection that could damage site trust or affect users. Prioritize inventory first, because unaffected sites require no action.
Technical view
The record describes a CWE-352 CSRF issue in etemplates ECT Social Share, package ect-social-share, allowing stored XSS. CVSS 3.1 is 7.1 high with network attack vector, low complexity, no attacker privileges, and required user interaction. Sources do not name a fixed version, patch details, or exploit procedure.
Likely exposure
Exposure is likely limited to WordPress sites with ECT Social Share installed at version 1.3 or earlier. Organizations without this plugin are not affected based on the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires user interaction and appears to rely on CSRF leading to stored XSS, but the provided sources do not include operational exploit details.
Researcher notes
Evidence is sparse: CVE and Patchstack identify CSRF to stored XSS through version 1.3, but do not provide a fixed version in the supplied bundle. Avoid assuming exploit availability or patch status. Validate exposure by plugin presence and version, then track vendor/Patchstack updates.
Mitigation direction
- Inventory WordPress sites for ECT Social Share installations.
- Check whether installed versions are 1.3 or earlier.
- Review Patchstack and vendor guidance for any fixed release or official mitigation.
- If no fixed release is available, consider disabling or removing the plugin.
- Prioritize admin awareness around suspicious links while remediation is pending.
Validation and detection
- Confirm plugin presence and version across production and staging WordPress sites.
- Review affected sites for unexpected stored scripts in plugin-controlled content or settings.
- Check WordPress admin activity for unusual setting changes around the disclosure period.
- Verify remediation by confirming the plugin is updated, disabled, or removed.
- Recheck public vulnerability sources for new patch or exploitation evidence.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-54405 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/ect-social-share/vulnerability/wordpress-ect-social-share-plugin-1-3-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.