Foyer <= 1.7.5 - Content Injection via Improper Access Control
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Foyer – Digital Signage for WordPress
- Affected Version
<= 1.7.5- CVSS
- 4.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2023-47663
At a glance
CVE-2023-47663 is a medium-severity Improper Authorization vulnerability in the Foyer WordPress plugin, affecting versions <= 1.7.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2023, reported by Abdi Pranata.
Vulnerability Overview
The Foyer – Digital Signage for WordPress plugin for WordPress is vulnerable to unauthorized content injection due to an insufficient capability check on the editing functionality in all versions up to, and including, 1.7.5. This makes it possible for authenticated attackers, with contributor access and above, to publish arbitrary content via slides.
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-285: Improper Authorization
Reaching this weakness in Foyer <= 1.7.5 takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. No fixed build of this plugin is recorded for Foyer yet, so installs running <= 1.7.5 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?
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. 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