CVE-2024-13568

Fluent Support – Helpdesk & Customer Support Ticket System <= 1.8.5 - Unauthenticated Sensitive Information Exposure Through Unprotected Directory

2025-02-28 15:27
Tim Coen

Strategic Overview

Status
Patched in 1.8.6
Affected Plugin
Fluent Support – Helpdesk & Customer Support Ticket System
Affected Version
<= 1.8.5
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-13568
View all Fluent Support – Helpdesk & Customer Support Ticket System vulnerabilities

At a glance

CVE-2024-13568 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Fluent Support WordPress plugin, affecting versions <= 1.8.5. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.8.6; sites on affected versions should update now. Disclosed February 2025, reported by Tim Coen.

Vulnerability Overview

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 sensitive data stored insecurely in the /wp-content/uploads/fluent-support directory which can contain file attachments included in support tickets.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Fluent Support <= 1.8.5 carries this weakness at fluent-support, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Fluent Support the fix is 1.8.6: builds <= 1.8.5 are affected, anything from 1.8.6 onward is not.

Remediation

Update to version 1.8.6, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Fluent Support 1.8.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13568https://www.wordfence.com/threat-intel/vulnerabilities/id/17f40832-8ae5-443a-aa98-f0e61d1152cchttps://nvd.nist.gov/vuln/detail/CVE-2024-13568

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C