WordPress Captivate Sync plugin <= 3.3.2 - SQL Injection vulnerability

published 2026-10-01 38 d ago modified 2026-10-01 38 d ago also EUVD-2026-90808

cvss: 7.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

captivateaudio Captivate Sync 3.3.3

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 38 d ago (2026-10-01)

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.6	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

Affected products

captivateaudio Captivate Sync

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/captivatesync-trade/vulnerability/wordpress-captivate-sync-plugin-3-3-2-sql-injecti
vdb-entry

Sources

CVE List CVE-2026-62060
NVD CVE-2026-62060

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary