Community by PeepSo <= 6.0.9.0 - Missing Authorization to Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 6.1.0.0
- Affected Plugin
- Community by PeepSo – Download from PeepSo.com
- Affected Version
<= 6.0.9.0- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-27630
At a glance
CVE-2023-27630 is a medium-severity Missing Authorization vulnerability in the Community by PeepSo WordPress plugin, affecting versions <= 6.0.9.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.0.0; sites on affected versions should update now. Disclosed May 2023, reported by Dave Jong.
Vulnerability Overview
The Community by PeepSo plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 6.0.9.0 due to missing authorization checks on the action_admin_export() function. This makes it possible for unauthenticated attackers to trigger a system report export and obtain sensitive information about the servers configuration.
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-862: Missing Authorization
Community by PeepSo <= 6.0.9.0 carries this weakness at action_admin_export(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Community by PeepSo the fix is 6.1.0.0: builds <= 6.0.9.0 are affected, anything from 6.1.0.0 onward is not.
Remediation
Update to version 6.1.0.0, or a newer patched version
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. None of that substitutes for the fix: Community by PeepSo 6.1.0.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Community by PeepSo – Download from PeepSo.com
- 8.8CVE-2016-10968: Community by PeepSo Privilege Escalation
CVE-2016-10968 - 8.1CVE-2023-25967: Community by PeepSo CSRF
CVE-2023-25967 - 6.5CVE-2026-66668: Community by PeepSo SQL Injection
CVE-2026-66668 - 6.5CVE-2024-25923: Community by PeepSo <= 6.2.7.0 Info Disclosure
CVE-2024-25923 - 6.4CVE-2023-47850: Community by PeepSo <= 6.2.2.0 Stored XSS
CVE-2023-47850 - 6.1CVE-2024-11447: Community by PeepSo Reflected XSS
CVE-2024-11447 - 6.1CVE-2024-0187: Community by PeepSo <= 6.3.1.1 Reflected XSS
CVE-2024-0187 - 6.1CVE-2023-48746: Community by PeepSo <= 6.2.6.0 Reflected XSS
CVE-2023-48746
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C