Podlove Podcast PublisherWordPress extension · Podlove
CVE-2016-10942
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 · uneditedThe podlove-podcasting-plugin-for-wordpress plugin before 2.3.16 for WordPress has SQL injection via the insert_id parameter exploitable via CSRF.
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 · high confidenceSQL injection vulnerability in the podlove-podcasting-plugin-for-wordpress plugin versions before 2.3.16 allows remote attackers to inject arbitrary SQL queries via the insert_id parameter, exploitable through CSRF attacks that trick an authenticated administrator into visiting a malicious page.
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
Podlove Podcast PublisherWordPress extension
< 2.3.16CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Podlove Podcast Publisher plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the 'podlove-podcasting-plugin-for-wordpress' or 'podlove-podcasting-plugin' folder, or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The plugin folder exists in the WordPress installation
-
Identify the installed plugin versionOpen the main plugin PHP file (usually podlove.php) in the plugin directory and locate the version comment in the file header, or check the version column in WordPress admin under Plugins > Installed PluginsAffected if The displayed version number is lower than 2.3.16 (e.g., 2.3.15, 2.3.14, etc.)
-
Check if the insert_id parameter is processedInspect the plugin PHP files for code handling the 'insert_id' GET or POST parameter, typically found in admin-facing files that handle episode or tracklist insertionsAffected if Code exists that processes the insert_id parameter without proper sanitization and the plugin version is below 2.3.16
-
Verify admin authentication is possibleConfirm that administrator accounts exist and have access to the WordPress admin dashboard where the vulnerable plugin functionality is accessibleAffected if Authenticated administrators can access the WordPress admin panel and the plugin's episode/tracklist management features
You are affected if the Podlove Podcast Publisher plugin is installed with a version lower than 2.3.16 and your WordPress admin panel is accessible, as the SQL injection can be triggered via a CSRF attack against an authenticated administrator.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3.16
Update the plugin to version 2.3.16 or later to remediate the SQL injection; until the update is applied, consider disabling the plugin or implementing additional CSRF protections.
2.3.16
- Backup your WordPress database and files before making any changes
- Navigate to the WordPress admin dashboard > Plugins > Installed Plugins
- Find 'Podlove Podcast Publisher' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 2.3.16 of the plugin
- Verify the plugin version shows 2.3.16 after updating
- Test that podcast publishing and playback functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Podlove Podcast Publisher
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10942 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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