LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10942: The podlove-podcasting-plugin-for-wordpress plugin before 2.3.16 for WordPress has SQL injection via the in...

The podlove-podcasting-plugin-for-wordpress plugin before 2.3.16 for WordPress has SQL injection via the insert_id parameter exploitable via CSRF.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Older Podlove Podcasting Plugin for WordPress versions had a SQL injection issue that could be triggered through a CSRF path. A vulnerable podcasting site may have exposed database-backed functionality if an authorized user was tricked into a malicious request. Public sources identify the fix boundary as versions before 2.3.16.

Executive priority

Treat this as a targeted legacy WordPress plugin risk. Prioritize verification where the plugin supports externally visible podcasting operations, but avoid emergency assumptions because the provided sources do not confirm active exploitation or severity scoring.

Technical view

CVE-2016-10942 describes SQL injection via the insert_id parameter in Podlove Podcasting Plugin for WordPress before 2.3.16, exploitable via CSRF. The provided bundle has no CVSS, CWE, affected CPE, or detailed exploitability data. Validation should focus on plugin presence, version, and vendor changelog evidence.

Likely exposure

Exposure is limited to WordPress sites running Podlove Podcasting Plugin versions earlier than 2.3.16. The bundle does not identify affected hosting platforms, WordPress versions, default reachability, or required user privileges.

Exploitation context

The CVE says exploitation is possible via CSRF, implying a user interaction or session context may be required. The source bundle does not show active exploitation, public exploit maturity, KEV listing, or weaponized details.

Researcher notes

The record is sparse: no CVSS vector, CWE mapping, CPE data, or detailed affected component path is provided. The key evidence is the CVE description and linked plugin/changelog/RIPS references. Do not infer broader Podlove Publisher impact beyond the named WordPress plugin and pre-2.3.16 boundary.

Mitigation direction

  • Check whether Podlove Podcasting Plugin is installed on WordPress sites.
  • Upgrade the plugin to version 2.3.16 or later if applicable.
  • Review vendor changelog and WordPress plugin page for current guidance.
  • Prioritize sites with authenticated administrators or editors using the plugin.

Validation and detection

  • Inventory WordPress sites for the Podlove Podcasting Plugin.
  • Confirm installed plugin versions are 2.3.16 or later.
  • Review logs for unusual requests involving insert_id where available.
  • Confirm CSRF protections and admin session handling around plugin workflows.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-10942 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.