CVE-2025-2011 in the critical feed json
Slider & Popup Builder by Depicter <= 3.6.1 - Unauthenticated SQL Injection via 's' Parameter
published 2025-05-06 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-13587
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 46.6%
- EPSS 46.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB, plus a Nuclei check
Summary
The Slider & Popup Builder by Depicter plugin for WordPress is vulnerable to generic SQL Injection via the ‘s' parameter in all versions up to, and including, 3.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Timeline
- Published
- First public exploit (Metasploit auxiliary/gather/wp_depicter_sqli_cve_2025_2011)
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
46.60% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/gather/wp_depicter_sqli_cve_2025_2011 WordPress Depicter Plugin SQL Injection (CVE-2025-2011) metasploit auxiliary, normal rank, 2025-05-08
- EDB-52285 WordPress Depicter Plugin 3.6.1 - SQL Injection webapps, 2025-05-09
- Nuclei template Slider & Popup Builder by Depicter <= 3.6.1 - Unauthenticated SQL Injection nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- averta Depicter — Popup & Slider Builder
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/49b36cde-39d8-4a69-8d7c-7b850b76a7cd?source=cve
- plugins.trac.wordpress.org /browser/depicter/trunk/app/src/Database/Repository/LeadRepository.php?rev=3156664#L224
- plugins.trac.wordpress.org /browser/depicter/trunk/app/src/Services/LeadService.php?rev=3156664#L82
- plugins.trac.wordpress.org /browser/depicter/trunk/app/src/Controllers/Ajax/LeadsAjaxController.php?rev=3156664#L23
- plugins.trac.wordpress.org /browser/depicter/trunk/app/src/Controllers/Ajax/LeadsAjaxController.php?rev=3156664#L49
- plugins.trac.wordpress.org /browser/depicter/trunk/app/src/Controllers/Ajax/LeadsAjaxController.php?rev=3156664#L179
- wordpress.org /plugins/depicter/#description
- plugins.trac.wordpress.org /changeset/3287525/
- github.com /datagoboom/CVE-2025-2011
Sources
- CVE List CVE-2025-2011
- NVD CVE-2025-2011
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.