Wise Chat <= 3.3.3 - Unauthenticated Sensitive Information Exposure Through Unprotected Directory
Strategic Overview
- Status
- Patched in 3.3.4
- Affected Plugin
- Wise Chat
- Affected Version
<= 3.3.2- CVSS
- 7.5High
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-13613
At a glance
CVE-2024-13613 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Wise Chat WordPress plugin, affecting versions <= 3.3.2. 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 3.3.4; sites on affected versions should update now. Disclosed May 2025, reported by Tim Coen.
Vulnerability Overview
The Wise Chat plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.3.3 via the 'uploads' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads directory which can contain file attachments included in chat messages. The vulnerability was partially patched in version 3.3.3.
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
Wise Chat <= 3.3.2 carries this weakness at uploads, 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 Wise Chat the fix is 3.3.4: builds <= 3.3.2 are affected, anything from 3.3.4 onward is not.
Remediation
Update to version 3.3.4, 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: Wise Chat 3.3.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Wise Chat
- 7.2CVE-2025-3774: Wise Chat <= 3.3.4 Stored Cross-Site Scripting
CVE-2025-3774 - 6.4CVE-2026-66636: Wise Chat <= 3.4 Stored Cross-Site Scripting
CVE-2026-66636 - 6.1CVE-2019-6780: Wise Chat <= 2.6.3 Reverse Tabnabbing
CVE-2019-6780 - 5.5Wise Chat <= 2.8.3 CSV Injection
- 4.3CVE-2023-32504: Wise Chat <= 3.1.3 Cross-Site Request Forgery
CVE-2023-32504
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C