Skip to main content

Captivate Sync CVE-2026-62060

| EUVDEUVD-2026-90808 HIGH
SQL Injection (CWE-89)
2026-10-01 Patchstack GHSA-gc7r-mx54-m2v7
7.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain high-privilege WordPress admin credentials
  2. Delivery
    Send crafted input to vulnerable Captivate Sync parameter
  3. Exploit
    Trigger blind SQL injection (boolean/time-based)
  4. Execution
    Infer and extract database contents row-by-row
  5. Impact
    Exfiltrate user hashes, secrets, and sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated high-privilege (administrator-level, PR:H) WordPress account on a site running the Captivate Sync plugin version 3.3.2 or earlier; the attacker then submits crafted input to the vulnerable plugin parameter. Exploitation is remote and needs no user interaction, but the high-privilege authentication requirement is the primary limiting factor - this is not exploitable by anonymous or low-privilege users. Because the injection is blind, successful data extraction also requires iterative boolean/time-based inference rather than direct output, modestly raising the practical effort.

Impact

This is a genuine but access-gated vulnerability that should be triaged as moderate rather than critical priority despite its 7.6 CVSS. The CVSS vector (AV:N/AC:L/PR:H/UI:N) confirms network-reachable, low-complexity exploitation requiring NO user interaction, but PR:H means the attacker must already hold high-privilege (administrator-level) WordPress credentials - this is the single biggest limiting factor and sharply narrows the realistic threat to insiders, compromised admin accounts, or multi-admin/agency sites where privilege boundaries matter. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so exploitation status is: no public exploit identified at time of analysis. The vendor rates scope-changed (S:C) with availability impact (A:L), which I find optimistic - a typical WordPress in-database blind SQL injection usually remains single-scope (S:U) and primarily confidentiality-affecting; I would assess C:H (full DB read including user hashes and secrets via blind boolean/time extraction) with no clear integrity or availability impact. Net: a real confidentiality risk on affected sites, but the PR:H precondition and absence of any exploitation signal (EPSS/KEV/POC) place it well below internet-wide-wormable issues. Verify the S:C and A:L claims with the vendor, as they drive the score above 7.0.

Exploit ScenarioDerived

An attacker who has obtained administrator-level access to a WordPress site running Captivate Sync ≤3.3.2 - via credential theft, a reused password, or a malicious/co-admin account on a shared or agency-managed site - submits crafted input to a vulnerable plugin parameter. Because the injection is blind, they use boolean- or time-based inference to extract data row-by-row from the WordPress database, such as other users' password hashes, API keys, and session secrets. No public proof-of-concept is available at this time, and no user interaction is required once the attacker is authenticated.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Blind SQL injection in the WordPress plugin Captivate Sync (all versions through 3.3.2) allows an authenticated administrator-level user to inject crafted SQL into a plugin parameter and extract database contents through boolean- or time-based inference. The vendor-published score is 7.6, but our independent assessment rates the true impact lower: exploitation requires a high-privilege (PR:H) WordPress account, the injection is blind so no direct query output is returned, and the demonstrated consequence is read-only disclosure of backend data rather than data modification or code execution. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this should be triaged as a moderate-priority, access-gated issue despite the headline CVSS number. It is most relevant to multi-author or managed WordPress installations where untrusted or over-privileged accounts hold administrator rights.

RemediationAI

No vendor-released patch version is identified in the available data, so the first step is to check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/captivatesync-trade/vulnerability/wordpress-captivate-sync-plugin-3-3-2-sql-injection-vulnerability?_s_id=cve) and the plugin's WordPress.org page for a release newer than 3.3.2 and apply it immediately if one exists; if no fix has been published, the safest action is to deactivate and remove Captivate Sync until a patched release is available, accepting the loss of whatever trade/sync functionality it provides. As a compensating control where deactivation is not operationally feasible, restrict the plugin to a staging or internal-only site, and reduce the attack surface by ensuring no account beyond a small, trusted set holds the administrator role - since exploitation requires PR:H, revoking and auditing administrator accounts (including stale ones) directly removes the prerequisite, though it does not fix the flaw itself and leaves any remaining admin capable of exploitation. A WAF or reverse proxy rule that filters anomalous SQL metacharacters on requests to the plugin's administrative endpoints can interrupt simple attempts, but boolean/time-based blind injection frequently evades signature rules, so this should be treated as detection-and-delay rather than prevention. Finally, because the vulnerability is read-only in effect, verify whether sensitive data such as user credentials or API keys reside in the WordPress database, and if so, rotate any secrets stored there after confirming or suspecting exploitation.

Affected VersionsENISA

Captivate Sync 0 ≤3.3.2

Affected Packages

euvd captivate_sync no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The underlying issue is CWE-89, improper neutralization of special elements used in an SQL command, in a WordPress plugin. Captivate Sync (the captivatesync-trade plugin from captivateaudio) constructs a SQL query from user-supplied input without adequate parameterization or escaping, so an attacker who can reach the vulnerable parameter can append or alter SQL syntax. Because the resulting queries do not return their results to the attacker, the flaw is a blind SQL injection: exploitation is performed iteratively, typically by observing TRUE/FALSE application responses (boolean-based) or by inducing measurable server delays (time-based), which is slower and noisier than classic in-band SQLi but equally capable of exfiltrating table contents when successful. The plugin executes inside the WordPress application context with the site's database credentials, so the blast radius is bounded by the privileges of the WordPress database user - which frequently has full read access to all wp_ tables. The CPE record cpe:2.3:a:captivateaudio:captivate_sync:*:*:*:*:*:*:*:* indicates that no version is excluded from the affected range up to and including 3.3.2, and the CVSS vector in the vendor record (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L) is more severe than our assessed vector (S:U/C:H/I:N/A:N); we treat our assessment as authoritative and therefore characterize the realistic impact as confidentiality-only, with no demonstrated integrity or availability effect and no scope change.

Know when Captivate Sync gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.6 HIGH
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 4.9 MEDIUM

Admin-level access is required (PR:H), the injection reaches the site's own database so scope is unchanged (S:U); blind SQLi yields full DB read (C:H) with no demonstrated integrity or availability impact.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in captivateaudio Captivate Sync captivatesync-trade allows Blind SQL Injection.This issue affects Captivate Sync: from n/a through 3.3.2.

Executive ViewAI

Why It Matters

The Captivate Sync WordPress plugin, versions through 3.3.2, represents a data-confidentiality risk for organizations that grant administrator rights to less-trusted or excessive WordPress accounts. The issue is access-gated and read-only, so the near-term business exposure is highest for multi-author, agency, or managed WordPress estates with poor admin hygiene. With no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, leadership should focus on governance and exposure reduction rather than incident escalation.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling or removing Captivate Sync versions through 3.3.2; enforcing least privilege and limiting administrator accounts to trusted users; deploying WAF rules to block boolean- and time-based SQL injection patterns in plugin parameters; and monitoring WordPress audit logs for anomalous read activity.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Low
niche podcast-hosting/sync WordPress plugin, limited deployment footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy