Skip to main content
VulnerabilityPublished

CVE-2026-62060: Captivate Sync (WordPress plugin) · SQL Injection

Affects Captivate Sync (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 3.3.3 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Captivate Sync (WordPress plugin) to 3.3.3.

Affected software

ProductAffectedFixed in
captivateaudioCaptivate SyncAffected
  • <3.3.3
Fixed in
  • 3.3.3

AI-suggested

If you cannot patch yet, restrict access to high-privilege accounts and monitor for suspicious activity related to SQL injection attempts.

Description

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.

References

Community reviews

Loading reviews…