Captivate Sync <= 3.3.2 - Authenticated (Editor+) SQL Injection via Episode Duplication
- ID
- WPSEC-2026-0091
- Plugin
- Captivate Sync (captivatesync-trade)
- Affected
- from 3.0.0 before 3.3.3
- Remediation
- Update to 3.3.3 or later.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Weakness
- CWE-89
- Usage
- Plugin Low · Affected versions Low among sites WPSec scans, 2026-10-22
- Attack surface
- Captivate Sync on WPSec AttackSurface
- Fix released
- Published
Description
The Captivate Sync plugin for WordPress is vulnerable to second-order SQL Injection via the episode duplication functionality (the duplicate-episode AJAX action) in versions 3.0.0 up to, and including, 3.3.2. This is due to the custom field (post meta) keys of the source episode being concatenated unescaped into a raw INSERT ... SELECT ... UNION ALL statement when the episode's meta is copied, instead of using prepared queries. This makes it possible for authenticated attackers with Editor-level access and above, who can add custom fields to any episode, to inject SQL through a crafted custom field name and trigger it by duplicating the episode. This can be used to extract sensitive information from the database or to insert arbitrary post meta rows. A Contributor or Author can also plant such a custom field on their own episode; it is triggered when an Editor or Administrator duplicates that episode.
References
- https://wpsec.com/vuln/WPSEC-2026-0091/
- https://plugins.svn.wordpress.org/captivatesync-trade/tags/3.3.3/
- https://wordpress.org/plugins/captivatesync-trade/
Published by WPSec. Provided as is, without warranty. Corrections: contact us.
This advisory as JSON or Markdown · All advisories: JSON, RSS