What this page helps you verify fast
This hub clusters every indexed record for Fluent Support – Helpdesk & Customer Support Ticket System so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Fluent Support – Helpdesk & Customer Support Ticket System (`fluent-support`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2025-67926, CVE-2025-57885 and CVE-2024-13568, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
Fluent Support – Helpdesk & Customer Support Ticket System <= 1.8.5 - Unauthenticated Sensitive Information Exposure Through Unprotected Directory
Fluent Support <= 1.5.7 - Authenticated (Administrator+) SQL Injection
Fluent Support <= 1.7.6 - Authenticated(Administrator+) SQL Injection
Fluent Support <= 1.8.0 - Authenticated (Subscriber+) SQL Injection
Fluent Support <= 1.8.0 - Insufficient Authorization on Email Verification
Fluent Support <= 1.10.4 - Missing Authorization
Fluent Support <= 1.9.1 - Cross-Site Request Forgery
This hub clusters every indexed record for Fluent Support – Helpdesk & Customer Support Ticket System so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to...
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.1. This is due to mi...
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.5 via the 'fluen...
Sorted by latest disclosure date so newly published issues surface first.
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 1.10.4. This makes it possible for authenticated attackers, with Subscrib...
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.9.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthentica...
The Fluent Support – Helpdesk & Customer Support Ticket System plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.5 via the 'fluent-support' directory. This makes it possible for unauthenticated attackers to extract sens...
The Fluent Support plugin for WordPress is vulnerable to unauthorized email verification due to insufficient validation on the sendSignupEmailVerificationHtml ()function in versions up to, and including, 1.8.0. This makes it possible for unauthenticated attackers to verify emails...
The Fluent Support plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 1.8.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attack...
The Fluent Support – WordPress Helpdesk and Customer Support Ticket Plugin plugin for WordPress is vulnerable to SQL Injection via an unknown parameter in all versions up to 1.7.7 (exclusive) due to insufficient escaping on the user supplied parameter and lack of sufficient prepa...
The Fluent Support plugin for WordPress is vulnerable to SQL Injection via an unknown parameter in versions up to, and including, 1.5.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible...