User Meta Manager < 3.4.8 - Missing Authorization to Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 3.4.8
- Affected Plugin
- User Meta Manager
- Affected Version
< 3.4.8- CVSS
- 6.5Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the User Meta Manager WordPress plugin, affecting versions < 3.4.8. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.4.8; sites on affected versions should update now. Disclosed February 2016, reported by Panagiotis Vagenas.
Vulnerability Overview
The User Meta Manager for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 3.4.7 via several functions called through unprotected AJAX actions. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to extract sensitive data including all data in the user meta table.
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. A successful exploit has high impact on confidentiality.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in User Meta Manager < 3.4.8 takes a caller who can reach the endpoint. 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 User Meta Manager the fix is 3.4.8: builds < 3.4.8 are affected, anything from 3.4.8 onward is not.
Remediation
Update to version 3.4.8, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: User Meta Manager 3.4.8 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in User Meta Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C