Skip to content
Web

CVE-2026-6147

8.8
High
EPSS 0.64%Patch availableAug 5, 2026

Authenticated arbitrary file upload in LightSync Pro WordPress plugin may enable RCE.

common questions

Is CVE-2026-6147 being exploited?

Not confirmed. CVE-2026-6147 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.

How severe is CVE-2026-6147?

CVE-2026-6147 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-6147?

Yes. A fix has been recorded for CVE-2026-6147. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-6147 affect?

CVE-2026-6147 affects WordPress LightSync Pro plugin <= 2.1.6, WordPress sites with plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-6147?

Update LightSync Pro to a patched version, restrict upload roles, scan for webshells.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress LightSync Pro plugin <= 2.1.6WordPress sites with plugin installed
impact

Authenticated users with Author+ can upload arbitrary files via rest_replace_media(), enabling remote code execution and site takeover.

action required

Patch when possible

affected versions
lightsyncpro LightSync Pro – Connect & Sync Cloud Assets | Lightroom, Canva, Figma, Dropbox & Shutterstock
  • affected<= 2.1.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free