Skip to content
Web

CVE-2026-34424

9.3
Critical
EPSS 0.55%Apr 10, 2026

Pre-auth RCE in Smart Slider 3 Pro via compromised updater; backdoors and admin accounts.

common questions

Is CVE-2026-34424 being exploited?

Not confirmed. CVE-2026-34424 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.

How severe is CVE-2026-34424?

CVE-2026-34424 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-34424?

Not known from our data. No patch reference has been recorded for CVE-2026-34424, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-34424 affect?

CVE-2026-34424 affects Smart Slider 3 Pro 3.5.1.35 on WordPress, Smart Slider 3 Pro 3.5.1.35 on Joomla. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-34424?

Upgrade to fixed version; disable updater; scan for backdoors

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Smart Slider 3 Pro 3.5.1.35 on WordPressSmart Slider 3 Pro 3.5.1.35 on Joomla
impact

Unauthenticated RCE; backdoors, new admin accounts, credential exfiltration, and persistence via injections.

action required

Immediate action required

affected versions
Nextendweb Smart Slider 3 Pro for Joomla
  • affected3.5.1.35
vendor says fixed in<= 3.5.1.34, 3.5.1.36
Nextendweb Smart Slider 3 Pro for WordPress
  • affected3.5.1.35
vendor says fixed in<= 3.5.1.34, 3.5.1.36

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free