dbcve.org
Sina Extension For ElementorWordPress extension · Sinaextra

CVE-2024-4373

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-15
Fix available
A fix is available. Upgrade to 3.5.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Sina Extension for Elementor (Slider, Gallery, Form, Modal, Data Table, Tab, Particle, Free Elementor Widgets & Elementor Templates) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Sina Particle Layer widget in all versions up to, and including, 3.5.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE-2024-35703 is likely a duplicate of this issue.

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

The Sina Extension for Elementor plugin fails to properly sanitize and escape user-supplied attributes in the Particle Layer widget, allowing authenticated users with contributor-level permissions or higher to inject malicious JavaScript through widget settings. This stored XSS executes whenever other users view pages containing the compromised widget.

MitigationUpdate the Sina Extension for Elementor plugin to version 3.5.4 or later which includes proper input sanitization and output escaping. Review user permissions and consider limiting contributor-level access until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sina Extension For ElementorWordPress extension
Affected:< 3.5.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Confirm Sina Extension for Elementor is installed
    Go to WordPress admin > Plugins and look for 'Sinaextra Sina Extension For Elementor' in the installed plugins list. Alternatively, check the plugins directory: /wp-content/plugins/
    Affected if The plugin is present in the plugins list
  2. Identify the installed plugin version
    In WordPress admin > Plugins, click on the plugin name to view details, or inspect the main plugin file header in /wp-content/plugins/sina-extension-for-elementor/ for the Version field
    Affected if Version is less than 3.5.4 or the Version field is not present (indicating an outdated install)
  3. Check if Particle Layer widget is in use
    In WordPress admin, go to Pages or Posts and edit any content. Search for 'Particle Layer' widget in Elementor panel search. Also inspect page content by searching the database: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%particle_layer%'
    Affected if Particle Layer widget is found on any published page or post
  4. Verify contributor-level user accounts exist
    In WordPress admin > Users, review the user list. Check user roles by inspecting wp_usermeta table: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%contributor%'
    Affected if At least one user account with contributor, author, editor, or administrator role exists (all roles above contributor can exploit this)
  5. Inspect saved widget settings for unsanitized input
    If Particle Layer is in use, examine saved widget settings in the database: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%elementor_data%' AND meta_value LIKE '%particle%'. Review the JSON data for Particle Layer settings fields
    Affected if Widget settings contain unescaped HTML characters like <script>, onerror=, or javascript: in any text fields

The environment is affected if Sina Extension for Elementor version is below 3.5.4 AND the Particle Layer widget is used on any site content AND users with contributor-level permissions exist.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.4 or later
Fixed in 3.5.4
Interim mitigation

Update the Sina Extension for Elementor plugin to version 3.5.4 or later which includes proper input sanitization and output escaping. Review user permissions and consider limiting contributor-level access until the patch is applied.

Recommended fix High confidence

3.5.4

  1. Upgrade the Sina Extension for Elementor plugin to version 3.5.4 or later from the WordPress plugin repository or your WordPress dashboard

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sina Extension For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4373 — 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-4373 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