Podlove Podcast Publisher <= 2.5.3 - Authenticated SQL Injection
Strategic Overview
- Status
- Patched in 2.6.0
- Affected Plugin
- Podlove Podcast Publisher
- Affected Version
< 2.6.0- CVSS
- 8.0High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2017-12949
At a glance
CVE-2017-12949 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Podlove Podcast Publisher WordPress plugin, affecting versions < 2.6.0. It carries a CVSS score of 8.0 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 2.6.0; sites on affected versions should update now. Disclosed August 2017, reported by Neven Birusk.
Vulnerability Overview
lib\modules\contributors\contributor_list_table.php in the Podlove Podcast Publisher plugin 2.5.3 and earlier for WordPress has SQL injection in the orderby parameter to wp-admin/admin.php, exploitable through CSRF.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in Podlove Podcast Publisher < 2.6.0 takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Podlove Podcast Publisher the fix is 2.6.0: builds < 2.6.0 are affected, anything from 2.6.0 onward is not.
Remediation
Update to version 2.6.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Podlove Podcast Publisher: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Podlove Podcast Publisher 2.6.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Podlove Podcast Publisher
- 9.8CVE-2026-13001: Podlove Podcast Publisher Arbitrary File Upload
CVE-2026-13001 - 9.8CVE-2025-10147: Podlove Podcast Publisher Arbitrary File Upload
CVE-2025-10147 - 8.8CVE-2026-16099: Podlove Podcast Publisher PHP Object Injection
CVE-2026-16099 - 8.8CVE-2024-43984: Podlove Podcast Publisher CSRF
CVE-2024-43984 - 8.8CVE-2016-10941: Podlove Podcast Publisher CSRF to Cross-Site Scripting
CVE-2016-10941 - 7.2CVE-2026-66615: Podlove Podcast Publisher <= 4.5.4 Stored XSS
CVE-2026-66615 - 7.2CVE-2024-52393: Podlove Podcast Publisher <= 4.1.15 RCE
CVE-2024-52393 - 6.4CVE-2026-75966: Podlove Podcast Publisher <= 4.5.5 Stored XSS
CVE-2026-75966
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C