SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent <= 3.4.8 - Authenticated (Customer+) Stored Cross-Site Scripting
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent has a cross-site scripting issue. Unsafe script can run in another user's browser if the vulnerable feature is used.
Quick answer
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent up to and including 3.4.8
Fixed versions
- SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent 3.4.9 or later
How to fix it
Update SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent. The old version can let unsafe script run in a user or admin browser.
- Back up the site and database.
- Update SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent to SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent 3.4.9 or later.
- Clear all site and plugin caches.
- Review recent posts, settings, forms, and widgets for unknown script.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent 3.4.9 or later.
- Test the affected feature and confirm script input is blocked or cleaned.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-57711?
SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent versions listed as affected should be reviewed: SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent up to and including 3.4.8.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.