CVE-2024-47302

Fluent Support <= 1.8.0 - Insufficient Authorization on Email Verification

2024-09-25 00:00
Khalid Yusuf

Strategic Overview

Status
Patched in 1.8.1
Affected Plugin
Fluent Support – Helpdesk & Customer Support Ticket System
Affected Version
<= 1.8.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-47302
View all Fluent Support – Helpdesk & Customer Support Ticket System vulnerabilities

At a glance

CVE-2024-47302 is a medium-severity Missing Authorization vulnerability in the Fluent Support WordPress plugin, affecting versions <= 1.8.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.1; sites on affected versions should update now. Disclosed September 2024, reported by Khalid Yusuf.

Vulnerability Overview

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 that do not belong to themselves.

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.

CWE-862: Missing Authorization

Reaching this weakness in Fluent Support <= 1.8.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Fluent Support the fix is 1.8.1: builds <= 1.8.0 are affected, anything from 1.8.1 onward is not.

Remediation

Update to version 1.8.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Fluent Support 1.8.1 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-47302https://www.wordfence.com/threat-intel/vulnerabilities/id/039ac1d9-ccb5-43d0-8b17-10d12b7df90ehttps://nvd.nist.gov/vuln/detail/CVE-2024-47302

Related records

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