Strategic Overview
- Status
- Patched in 5.1.3
- Affected Plugin
- All-In-One Security (AIOS) – Security and Firewall
- Affected Version
<= 5.1.2- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2022-4346
At a glance
CVE-2022-4346 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the All-In-One Security (AIOS) WordPress plugin, affecting versions <= 5.1.2. 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 5.1.3; sites on affected versions should update now. Disclosed December 2022, reported by Daniel Ruf.
Vulnerability Overview
The All-In-One Security plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 5.1.2. This is due to the plugin allowing administrators to upload backups to publicly accessible folders for restoring purposes. While under normal use these files would be deleted as part of the restore process, it is possible they are left behind when the restore is abandoned. This could allow unauthenticated attackers to extract sensitive user or configuration data under rare circumstances in certain server configurations.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in All-In-One Security (AIOS) <= 5.1.2 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 All-In-One Security (AIOS) the fix is 5.1.3: builds <= 5.1.2 are affected, anything from 5.1.3 onward is not.
Remediation
Update to version 5.1.3, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: All-In-One Security (AIOS) 5.1.3 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in All-In-One Security (AIOS) – Security and Firewall
- 9.8CVE-2016-10887: All In One WP Security & Firewall SQL Injection
CVE-2016-10887 - 9.8CVE-2016-10888: All In One WP Security & Firewall SQL Injection
CVE-2016-10888 - 9.8CVE-2015-9310: All In One WP Security & Firewall SQL Injection
CVE-2015-9310 - 9.0CVE-2015-0894: All In One WP Security & Firewall SQL Injection
CVE-2015-0894 - 8.8CVE-2022-44737: All In One WP Security & Firewall <= 5.1.0 CSRF
CVE-2022-44737 - 8.8All In One WP Security & Firewall <= 5.1.0 Cross-Site Request Forgery
- 7.4CVE-2014-6242: All In One WP Security & Firewall Access or CSRF
CVE-2014-6242 - 7.2CVE-2026-8438: All-In-One Security (AIOS) <= 5.4.7 Stored XSS
CVE-2026-8438
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C