MAS Static Content <= 1.0.8 - Authenticated (Contributor+) Private Static Content Page Disclosure
Strategic Overview
- Status
- Patched in 1.0.9
- Affected Plugin
- MAS Static Content
- Affected Version
<= 1.0.8- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-8483
At a glance
CVE-2024-8483 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the MAS Static Content WordPress plugin, affecting versions <= 1.0.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.0.9; sites on affected versions should update now. Disclosed September 2024, reported by emad.
Vulnerability Overview
The MAS Static Content plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 1.0.8 via the static_content() function. This makes it possible for authenticated attackers, with contributor-level access and above, to extract potentially sensitive information from private static content pages.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
MAS Static Content <= 1.0.8 carries this weakness at static_content(), and reaching it takes an account at Contributor level or above. 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 MAS Static Content the fix is 1.0.9: builds <= 1.0.8 are affected, anything from 1.0.9 onward is not.
Remediation
Update to version 1.0.9, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: MAS Static Content 1.0.9 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C