dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4341

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Prime Slider – Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'follow_us_text' setting of the Mount widget in all versions up to, and including, 4.1.10. This is due to insufficient input sanitization and output escaping. Specifically, the `render_social_link()` function in `modules/mount/widgets/mount.php` outputs the `follow_us_text` Elementor widget setting using `echo` without any escaping function. The setting value is stored in `_elementor_data` post meta via `update_post_meta`. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Prime Slider plugin for WordPress contains a stored XSS vulnerability in the Mount widget where the 'follow_us_text' setting is stored without input sanitization and output without escaping. The render_social_link() function in modules/mount/widgets/mount.php uses echo to output the setting value directly, allowing authenticated Author+ users to inject malicious JavaScript that executes on page access.

MitigationUpdate the Prime Slider plugin to version 4.1.11 or later which includes proper input sanitization and output escaping for the follow_us_text parameter.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Prime Slider plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Prime Slider. Check the version number displayed. Alternatively, check the plugin files in wp-content/plugins/prime-slider/ for a version definition.
    Affected if The installed version is lower than 4.1.11, as versions prior to this lack proper output escaping in render_social_link()
  2. Identify if Mount widget is in use
    Review pages and posts created with Elementor that use the Prime Slider Mount widget. Check Elementor editor data or inspect the post content for evidence of the Mount widget shortcode or template.
    Affected if The Mount widget from Prime Slider is actively used on the site, as this is the specific widget containing the vulnerable render_social_link() function
  3. Inspect Elementor post meta for follow_us_text
    Query the WordPress database: SELECT * FROM wp_postmeta WHERE meta_key = 'follow_us_text' (adjust prefix if different). Examine the meta_value field for any injected scripts or unusual HTML attributes.
    Affected if The follow_us_text meta_value contains unescaped HTML tags such as <script>, event handlers like onmouseover, or javascript: URIs, indicating exploitation
  4. Examine mount.php for unescaped output in render_social_link()
    Locate the mount.php file in the Prime Slider plugin directory (typically wp-content/plugins/prime-slider/modules/mount/widgets/mount.php). Open the file and locate the render_social_link() function. Inspect echo statements within this function.
    Affected if The render_social_link() function contains echo statements that output the follow_us_text value without using esc_html() or esc_attr() functions, leaving user input unescaped

You are affected if Prime Slider version is below 4.1.11 AND the Mount widget is in use, with the render_social_link() function outputting follow_us_text without proper escaping.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Prime Slider plugin to version 4.1.11 or later which includes proper input sanitization and output escaping for the follow_us_text parameter.

Recommended fix High confidence

Prime Slider – Addons for Elementor version 4.1.11

  1. Upgrade the Prime Slider – Addons for Elementor plugin to version 4.1.11 or later via the WordPress plugin repository or WordPress admin dashboard

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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