dbcve.org
Testimonial Carousel For ElementorWordPress extension · Uapp

CVE-2024-35713

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-08
Fix available
A fix is available. Upgrade to 10.2.0 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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in UAPP GROUP Testimonial Carousel For Elementor allows Stored XSS.This issue affects Testimonial Carousel For Elementor: from n/a through 10.1.1.

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

A stored XSS vulnerability exists in the Testimonial Carousel For Elementor WordPress plugin where user-supplied input in testimonial fields is not properly sanitized before being rendered in the page, allowing attackers to inject malicious JavaScript code that executes when other users view the affected content.

MitigationUpdate the plugin to the latest version when available. In the interim, restrict access to the testimonial submission functionality to trusted users only and implement additional output escaping where testimonials are displayed.

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
Testimonial Carousel For ElementorWordPress extension
Affected:< 10.2.0

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. Verify the plugin is installed
    Check if Uapp Testimonial Carousel For Elementor is present in your WordPress installation, either via the Plugins admin page or by examining the wp-content/plugins directory for a testimonial-carousel-for-elementor folder.
    Affected if The plugin is installed and active.
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Testimonial Carousel For Elementor' to view the installed version number. Compare this to the affected range of versions below 10.2.0.
    Affected if The installed version is any version prior to 10.2.0.
  3. Confirm testimonial submission is accessible
    Navigate to the testimonial submission form on your site if one exists, or check the plugin settings to determine whether unauthenticated or low-privilege users can submit testimonials.
    Affected if Testimonial submission is available to untrusted users or the public.
  4. Inspect existing testimonials for suspicious content
    Access the testimonial management section in WordPress admin (usually under the plugin menu) and review stored testimonials for any unusual script tags, JavaScript event handlers, or encoded characters that may indicate injected XSS payloads.
    Affected if Any testimonial entries contain unsanitized JavaScript code or suspicious HTML/script elements.

You are affected if the plugin version is below 10.2.0 and testimonial submission is accessible to users who should not be trusted with code execution capabilities.

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 10.2.0 or later
Fixed in 10.2.0
Interim mitigation

Update the plugin to the latest version when available. In the interim, restrict access to the testimonial submission functionality to trusted users only and implement additional output escaping where testimonials are displayed.

Recommended fix High confidence

10.2.0

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress Admin > Plugins
  3. Locate 'Testimonial Carousel For Elementor' in the plugins list
  4. Click 'Update now' or 'Update' to upgrade to version 10.2.0 or the latest available version
  5. Verify the update completed successfully by checking the plugin version

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

Fix this in Testimonial Carousel For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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