Description
The Slider Hero plugin for WordPress is vulnerable to second-order SQL Injection in versions up to, and including, 9.1.7 via the qcld_sliderhero_duplicate() function. Slide data (description, title, btn, btn2, image_link, custom, etc.) is stored safely via $wpdb->update() with %s placeholders in the qchero_save_image AJAX handler, but when an administrator triggers the 'heroduplicateslider' task, qcld_sliderhero_duplicate() re-reads every slide column and concatenates the raw values directly into an INSERT VALUES tuple that is then executed with $wpdb->query() — with no $wpdb->prepare(), esc_sql(), or _real_escape_string in between. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
References6
- plugins.trac.wordpress.org/browser/slider-hero/tags/9.1.6/qcld-…
- plugins.trac.wordpress.org/browser/slider-hero/tags/9.1.6/qcld-…
- plugins.trac.wordpress.org/browser/slider-hero/tags/9.1.7/qcld-…
- plugins.trac.wordpress.org/browser/slider-hero/tags/9.1.7/qcld-…
- plugins.trac.wordpress.org/changeset?reponame=&old=3635315%40sl…
- www.wordfence.com/threat-intel/vulnerabilities/id/c2b36621-3322…
Metrics
- CVSS 3.1
-
4.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 42 · as of 11 November 2026
- CWE
- CWE-89
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.