All-in-One Security vulnerability history, read beside its lockout, firewall and account screens
Titles in the All-in-One Security (AIOS) history carry the words Two-Factor Authentication, Renamed Login Page, IP Blocking and Captcha, features the plugin adds.
Match each record on its version fields, then write down what each screen shows.
On this page
All-in-One Security vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 29 records for All-in-One Security. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 5.5.0
Worked out from data retrieved on .
Every affected range listed in this source for All-in-One Security ends before version 5.5.0.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Two Factor Authentication < 1.17.0 and All-In-One Security (AIOS) <= 5.4.0 - Authenticated (Subscriber+) Two-Factor Authentication Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2026-111739
Affected versions- All versions up to and including 5.4.0
Patched versions: 5.5.0
Update to at least version 5.5.0.
All-In-One Security (AIOS) - Security and Firewall <= 5.4.8 - Authenticated (Subscriber+) Security Control Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.3)
- CVE:
- CVE-2026-96825
Affected versions- All versions up to and including 5.4.8
Patched versions: 5.4.9
Update to at least version 5.4.9.
All-In-One Security (AIOS) <= 5.4.7 - Unauthenticated Stored Cross-Site Scripting via REST API Request Path
- Published:
- Last updated:
- Severity:
- High (CVSS 7.2)
- CVE:
- CVE-2026-8438
Affected versions- All versions up to and including 5.4.7
Patched versions: 5.4.8
Update to at least version 5.4.8.
All In One WP Security <= 5.2.6 - Cross-Site Request Forgery to IP Blocking
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2024-30468
Affected versions- All versions up to and including 5.2.6
Patched versions: 5.2.7
Update to at least version 5.2.7.
All-In-One Security (AIOS) - Security and Firewall <= 5.2.5 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-1037
Affected versions- All versions up to and including 5.2.5
Patched versions: 5.2.6
Update to at least version 5.2.6.
Show 24 older recordsHide the older records
All In One WP Security <= 5.2.4 - Protection Bypass of Renamed Login Page via URL Encoding
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2023-52147
Affected versions- All versions before 5.2.5
Patched versions: 5.2.5
Update to at least version 5.2.5.
All In One WP Security 5.1.9 - Plaintext Storage of Credentials
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.9)
Affected versions- Version 5.1.9 only
Patched versions: 5.2.0
Update to at least version 5.2.0.
All-In-One Security (AIOS) <= 5.1.4 - Authenticated (Admin+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.4)
- CVE:
- CVE-2023-0157
Affected versions- All versions up to and including 5.1.4
Patched versions: 5.1.5
Update to at least version 5.1.5.
All-In-One Security (AIOS) <= 5.1.4 - Authenticated(Admin+) Directory Traversal
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.9)
- CVE:
- CVE-2023-0156
Affected versions- All versions up to and including 5.1.4
Patched versions: 5.1.5
Update to at least version 5.1.5.
All-In-One Security <= 5.1.2 - Information Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2022-4346
Affected versions- All versions up to and including 5.1.2
Patched versions: 5.1.3
Update to at least version 5.1.3.
All In One WP Security & Firewall <= 5.1.0 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
- CVE:
- CVE-2022-44737
Affected versions- All versions up to and including 5.1.0
Patched versions: 5.1.1
Update to at least version 5.1.1.
All-In-One Security (AIOS) - Security and Firewall <= 5.0.8 - IP Spoofing to Protection Mechanism Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
- CVE:
- CVE-2022-4097
Affected versions- All versions up to and including 5.0.7
Patched versions: 5.0.8
Update to at least version 5.0.8.
All In One WP Security & Firewall <= 5.1.0 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
Affected versions- All versions up to and including 5.1.0
Patched versions: 5.1.1
Update to at least version 5.1.1.
All In One WP Security & Firewall 5.0.0 - 5.0.7 - Protection Bypass via IP Spoofing
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- From version 5.0.0 up to and including 5.0.7
Patched versions: 5.0.8
Update to at least version 5.0.8.
All In One WP Security & Firewall <= 4.4.10 - Open Redirect and Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2021-25102
Affected versions- All versions before 4.4.11
Patched versions: 4.4.11
Update to at least version 4.4.11.
All In One WP Security & Firewall <= 4.4.5 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2020-29171
Affected versions- All versions before 4.4.6
Patched versions: 4.4.6
Update to at least version 4.4.6.
All In One WP Security & Firewall <= 4.4.3 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.7)
Affected versions- All versions up to and including 4.4.3
Patched versions: 4.4.4
Update to at least version 4.4.4.
All In One WP Security & Firewall <= 4.0.8 - SQL Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2016-10887
Affected versions- All versions before 4.0.9
Patched versions: 4.0.9
Update to at least version 4.0.9.
All In One WP Security & Firewall <= 4.1.9 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2016-10866
Affected versions- All versions before 4.2.0
Patched versions: 4.2.0
Update to at least version 4.2.0.
All In One WP Security & Firewall <= 4.1.2 - Captcha Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions- All versions up to and including 4.1.2
Patched versions: 4.1.3
Update to at least version 4.1.3.
All In One WP Security & Firewall <= 4.0.6 - SQL Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2016-10888
Affected versions- All versions before 4.0.7
Patched versions: 4.0.7
Update to at least version 4.0.7.
All In One WP Security & Firewall <= 4.0.5 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2016-10867
Affected versions- All versions before 4.0.6
Patched versions: 4.0.6
Update to at least version 4.0.6.
All In One WP Security & Firewall <= 4.0.4 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2016-10868
Affected versions- All versions before 4.0.5
Patched versions: 4.0.5
Update to at least version 4.0.5.
All In One WP Security & Firewall <= 3.9.7 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2015-9293
Affected versions- All versions before 3.9.8
Patched versions: 3.9.8
Update to at least version 3.9.8.
All In One WP Security & Firewall <= 3.9.4 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2015-9294
Affected versions- All versions before 3.9.5
Patched versions: 3.9.5
Update to at least version 3.9.5.
All In One WP Security & Firewall <= 3.9.0 - SQL Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.8)
- CVE:
- CVE-2015-9310
Affected versions- All versions before 3.9.1
Patched versions: 3.9.1
Update to at least version 3.9.1.
All In One WP Security & Firewall <= 3.8.9 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- Low (CVSS 3.1)
- CVE:
- CVE-2015-0895
Affected versions- All versions up to and including 3.8.9
Patched versions: 3.9.0
Update to at least version 3.9.0.
All In One WP Security & Firewall <= 3.8.7 - SQL Injection
- Published:
- Last updated:
- Severity:
- Critical (CVSS 9.0)
- CVE:
- CVE-2015-0894
Affected versions- All versions before 3.8.8
Patched versions: 3.8.8
Update to at least version 3.8.8.
All In One WP Security & Firewall <= 3.8.2 - Authenticated Access or Cross-Site Request Forgery leading to SQL Injection via orderby, order Parameters
- Published:
- Last updated:
- Severity:
- High (CVSS 7.4)
- CVE:
- CVE-2014-6242
Affected versions- All versions before 3.8.3
Patched versions: 3.8.3
Update to at least version 3.8.3.
Check All-in-One Security on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What All-in-One Security adds to WordPress, and who can reach it
All-in-One Security (AIOS) is published on WordPress.org by David Anderson / Team Updraft.
Its listing says it includes login security features, file and database security, a firewall, spam prevention and an audit log, and the listing's FAQ calls AIOS Premium an add-on that requires the free version to be present.
The vendor's install guide has settings adjusted from the plugin's own admin menu, but the vendor's text names two routes that take input from other people. The plugin's text describes the lockout screen's Allow unlock requests option as allowing users to generate an automated unlock request link which will unlock their account, and the vendor's two-factor guide lists a shortcode, twofactor_user_settings, that allows a site's users to get and set their TFA settings.
Access wordings in the history's titles include Unauthenticated, Authenticated (Subscriber+) and Authenticated (Admin+). In WordPress's own documentation the Subscriber role holds only the read capability. As this page's own step, read Settings > General: Anyone can register lets anyone register an account when ticked, and New User Default Role assigns the role the new account receives.
Reading All-in-One Security vulnerabilities by field, not by name or title
Every record in the history is filed under one slug, all-in-one-wp-security-and-firewall, but titles use several names for the plugin, among them All In One WP Security & Firewall, All In One WP Security and All-In-One Security (AIOS).
Title phrases that recur include Cross-Site Scripting, SQL Injection and Bypass. Compare the installed version with each record's affected range and patched versions field, not with the number in its title.
- CVE-2026-111739, whose title opens Two Factor Authentication < 1.17.0 and ends Authenticated (Subscriber+) Two-Factor Authentication Bypass. Affected: all versions up to and including 5.4.0. Patched: 5.5.0. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
- CVE-2026-96825, whose title ends Authenticated (Subscriber+) Security Control Bypass. Affected: all versions up to and including 5.4.8. Patched: 5.4.9.
- CVE-2026-8438, whose title ends Unauthenticated Stored Cross-Site Scripting via REST API Request Path. Affected: all versions up to and including 5.4.7. Patched: 5.4.8.
- CVE-2022-4097, whose title ends <= 5.0.8 - IP Spoofing to Protection Mechanism Bypass. Its fields differ from that number. Affected: all versions up to and including 5.0.7. Patched: 5.0.8.
The AIOS changelog as a second place to read
Before relying on the update guidance at the top of the history, read the changelog on the plugin's WordPress.org listing, which starts some lines with the word SECURITY, among them lines about login lockout unlock requests and TFA codes: a release the vendor marks that way may have no record on this page.
Carrying out the five checks in the AIOS menus
Each step is a read on a site you are authorised to review.
AIOS screens put Save buttons and file operations beside the values being read: change no switch, save nothing, and press no backup, restore, import or export button.
The vendor's pages name the menu two ways: its install guide says WP Security, while the listing's installation steps say AIOS and a changelog line there records the menu item being renamed from WP Security to AIOS. Paths quoted here keep each page's own wording.
WordPress gives each plugin's version number in the Description column of the Plugins screen. The listing's FAQ says to keep the free version installed and active under Premium, and the vendor's install guide names the paid row AIOS Premium (All-in-One Security and Firewall Premium).
Write down the version and the Automatic update column for each row. The free plugin's row is the one to set against the affected ranges in the history.
The vendor's locked-out page gives the allow list's path in full, WP Security > Firewall > Block and Allow Lists > Allow List, and says allowlisting an IP there ensures it bypasses all firewall rules. Copy both lists in full.
Two more headings in the plugin's text are PHP firewall settings, whose rule groups include nG firewall rules and WP REST API, and .htaccess firewall settings, whose groups are Basic firewall settings, Block debug log and Listing directory content.
Write down the state of each switch. A changelog line on the listing describes a whitelist and user role-based access limit in the REST API firewall: copy both. Record the web server too, because the listing's FAQ says features that use the .htaccess file will not apply on a Windows IIS server or NGINX server (it adds that porting them is in development).
For the login lockdown check, the vendor's locked-out page finds Max Login Attempts at WP Security > Brute Force > Login Attempts. The plugin's text puts that field under the heading Login lockout configuration, so search for the heading if the path differs. Write down Enable login lockout feature, Allow unlock requests, Max login attempts, Login retry time period (min), both lockout time lengths and the addresses under Notify by email.
Copy the Login lockout IP whitelist too: the text says its addresses will never be blocked by the login lockout feature.
Cookie-based brute force prevention is a separate feature, which the vendor places two ways: the locked-out page at WP Security > Brute Force, the brute force guide at WP Security > Firewall > Brute Force Prevention. The guide says a secret word creates a special URL that deposits a cookie, and that a user without it is redirected to an address you configure.
Note whether the feature is enabled, not the secret word. Then read wp-config.php for a line the locked-out page gives as a way to disable features temporarily, defining AIOS_DISABLE_COOKIE_BRUTE_FORCE_PREVENTION as true.
Among its login security entries, the listing describes identifying default admin usernames and detecting cases where the display name matches the username. Changelog lines on the listing call the screen User Security > User Accounts, and the plugin's text divides it into Admin user security, Display name security, User enumeration settings and Password settings.
Under the heading Change admin username, the text has a box titled List of administrator accounts. Under Modify accounts with identical login name and display name, the screen either lists such accounts or says No action required. Write down what each shows and change nothing.
Then set the plugin's administrator list beside the Administrator filter link on the WordPress Users screen, and note which roles have to use TFA: the listing describes requiring it for specific user roles.
The vendor's export guide starts at WP Admin > WP Security > Settings, on the Import/Export tab, and the plugin's text has a screen headed Export or import your AIOS settings. The same guide describes a wp-config.php File tab whose backup button brings a download prompt for a file named wp-config-backup.txt, and says wp-config.php includes database credentials, password salts and keys.
The check is who could press those buttons, not what they produce: start the list with the holders of the Administrator role, from the Role column of the Users screen, and ask where earlier exports and backup files are kept.
The import form in the plugin's text has fields labelled Email, Secret word, Renamed login page url, Site key and Secret key, under a note about importing settings from another site domain. Handle an exported settings file as you would those values, and leave the import form alone: the guide warns that importing settings blindly can cause you to be locked out of your site.
AIOS plugin security beyond a version match
A match between the installed AIOS version and an affected range is about the release, not the site.
It cannot tell you whether the flaw was ever used, whether login lockout is switched on, which addresses the allow list and the lockout whitelist exempt, or who holds an exported settings file.
Nor does it reach settings changed outside the screens: the vendor's WP-CLI page lists commands, which it says need SSH access, the WordPress Command Line Interface installed and AIOS Security and Firewall Premium activated, that include wp aios set firewall off and wp aios set login-lockout off. List who has shell access.
A WordPress security audit sends a measured run of failed logins to wp-login.php and xmlrpc.php and records whether, and when, the site starts refusing them. It also matches each administrator account to a named person and looks for a user called admin.
Frequently asked questions
The ranges differ from record to record, so check the installed version against all of them. CVE-2026-8438 covers all versions up to and including 5.4.7 and lists 5.4.8 as patched, while CVE-2022-4097 covers all versions up to and including 5.0.7 and lists 5.0.8. Then read the update guidance at the top of the history.
The Plugins screen gives the installed version in its Description column, and WordPress's documentation says an update notice appears there if a plugin is hosted in the Plugin Directory and a newer version is available. For AIOS Premium, the vendor's install guide says receiving updates means connecting a TeamUpdraft account from the Premium row, and the listing's FAQ says development and test sites require their own licence if updates to the plugin are needed, so compare a staging copy's versions with the live site's.
The records here are the ones the source data files under the slug all-in-one-wp-security-and-firewall, the free plugin's address on WordPress.org. Being filed there does not settle whether a record applies to Premium. The listing's FAQ says the premium extends the free version, which has to be installed and activated first, so a Premium site runs the free plugin too: compare that version with the affected ranges.
That depends on retention settings, so write them down before reading the logs for signs that a flaw was used. Changelog lines on the listing say audit log data retention settings were added, the default audit log retention period was changed to 30 days, and login lockdown table records are purged after 90 days unless a constant, AIOS_PURGE_LOGIN_LOCKOUT_RECORDS_AFTER_DAYS, changes the default.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 24 of the 29 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Two Factor Authentication < 1.17.0 and All-In-One Security (AIOS) <= 5.4.0 - Authenticated (Subscriber+) Two-Factor Authentication Bypass (CVE-2026-111739)
- All-In-One Security (AIOS) - Security and Firewall <= 5.4.8 - Authenticated (Subscriber+) Security Control Bypass (CVE-2026-96825)
- All-In-One Security (AIOS) <= 5.4.7 - Unauthenticated Stored Cross-Site Scripting via REST API Request Path (CVE-2026-8438)
- All In One WP Security <= 5.2.6 - Cross-Site Request Forgery to IP Blocking (CVE-2024-30468)
- All-In-One Security (AIOS) - Security and Firewall <= 5.2.5 - Reflected Cross-Site Scripting (CVE-2024-1037)
- All In One WP Security <= 5.2.4 - Protection Bypass of Renamed Login Page via URL Encoding (CVE-2023-52147)
- All In One WP Security 5.1.9 - Plaintext Storage of Credentials
- All-In-One Security (AIOS) <= 5.1.4 - Authenticated (Admin+) Stored Cross-Site Scripting (CVE-2023-0157)
- All-In-One Security (AIOS) <= 5.1.4 - Authenticated(Admin+) Directory Traversal (CVE-2023-0156)
- All-In-One Security <= 5.1.2 - Information Disclosure (CVE-2022-4346)
- All In One WP Security & Firewall <= 5.1.0 - Cross-Site Request Forgery (CVE-2022-44737)
- All-In-One Security (AIOS) - Security and Firewall <= 5.0.8 - IP Spoofing to Protection Mechanism Bypass (CVE-2022-4097)
- All In One WP Security & Firewall <= 5.1.0 - Cross-Site Request Forgery
- All In One WP Security & Firewall 5.0.0 - 5.0.7 - Protection Bypass via IP Spoofing
- All In One WP Security & Firewall <= 4.4.10 - Open Redirect and Reflected Cross-Site Scripting (CVE-2021-25102)
- All In One WP Security & Firewall <= 4.4.5 - Cross-Site Scripting (CVE-2020-29171)
- All In One WP Security & Firewall <= 4.4.3 - Reflected Cross-Site Scripting
- All In One WP Security & Firewall <= 4.0.8 - SQL Injection (CVE-2016-10887)
- All In One WP Security & Firewall <= 4.1.9 - Reflected Cross-Site Scripting (CVE-2016-10866)
- All In One WP Security & Firewall <= 4.1.2 - Captcha Bypass
- All In One WP Security & Firewall <= 4.0.6 - SQL Injection (CVE-2016-10888)
- All In One WP Security & Firewall <= 4.0.5 - Cross-Site Scripting (CVE-2016-10867)
- All In One WP Security & Firewall <= 4.0.4 - Cross-Site Scripting (CVE-2016-10868)
- All In One WP Security & Firewall <= 3.9.7 - Cross-Site Scripting (CVE-2015-9293)
- All In One WP Security & Firewall <= 3.9.4 - Reflected Cross-Site Scripting (CVE-2015-9294)
- All In One WP Security & Firewall <= 3.9.0 - SQL Injection (CVE-2015-9310)
- All In One WP Security & Firewall <= 3.8.9 - Cross-Site Request Forgery (CVE-2015-0895)
- All In One WP Security & Firewall <= 3.8.7 - SQL Injection (CVE-2015-0894)
- All In One WP Security & Firewall <= 3.8.2 - Authenticated Access or Cross-Site Request Forgery leading to SQL Injection via orderby, order Parameters (CVE-2014-6242)