WP Guppy: Sensitive information exposure
WP Guppy is affected by sensitive information exposure. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can disclose data that should not be available to the caller.
- Component
- WP Guppy
- Plugin slug
wp-guppy- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Dec 27, 2021
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Dec 27, 2021 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update WP Guppy to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The WP Guppy WordPress plugin before 1.3 does not have any authorisation in some of the REST API endpoints, allowing any user to call them and could lead to sensitive information disclosure, such as usernames and chats between users, as well as be able to send messages as an arbitrary user
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N