Featured Video Plus <= 2.3.3 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Featured Video Plus
- Affected Version
<= 2.3.3- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-66685
At a glance
CVE-2026-66685 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Featured Video Plus WordPress plugin, affecting versions <= 2.3.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Ananda Dhakal.
Vulnerability Overview
The Featured Video Plus plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 2.3.3. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Featured Video Plus <= 2.3.3 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. No fixed build of this plugin is recorded for Featured Video Plus yet, so installs running <= 2.3.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C