XPlainer – WooCommerce Product FAQ [WooCommerce Accordion FAQ Plugin] <= 1.7.0 - Missing Authorization to Authenticated (Subscriber+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.7.1
- Affected Plugin
- Happy FAQs – WordPress FAQ and Product FAQ
- Affected Version
<= 1.7.0- CVSS
- 6.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-5669
At a glance
CVE-2024-5669 is a medium-severity Missing Authorization vulnerability in the Happy FAQs WordPress plugin, affecting versions <= 1.7.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.7.1; sites on affected versions should update now. Disclosed July 2024, reported by Lucio Sá.
Vulnerability Overview
The XPlainer – WooCommerce Product FAQ [WooCommerce Accordion FAQ Plugin] plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'ffw_activate_template' function in all versions up to, and including, 1.7.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to store cross-site scripting that will trigger when viewing the dashboard templates or accessing FAQs.
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 interaction from a victim user.
CWE-862: Missing Authorization
Happy FAQs <= 1.7.0 carries this weakness at ffw_activate_template, and reaching it takes an account at Subscriber level or above. 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 Happy FAQs the fix is 1.7.1: builds <= 1.7.0 are affected, anything from 1.7.1 onward is not.
Remediation
Update to version 1.7.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: Happy FAQs 1.7.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Happy FAQs – WordPress FAQ and Product FAQ
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C