Security Optimizer – The All-In-One Protection Plugin <= 1.5.0 - Missing Authorization via hide_notice()
Strategic Overview
- Status
- Patched in 1.5.1
- Affected Plugin
- Security Optimizer – The All-In-One Protection Plugin
- Affected Version
<= 1.5.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-38774
At a glance
CVE-2024-38774 is a medium-severity Missing Authorization vulnerability in the Security Optimizer WordPress plugin, affecting versions <= 1.5.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.5.1; sites on affected versions should update now. Disclosed July 2024, reported by Rafie Muhammad.
Vulnerability Overview
The Security Optimizer – The All-In-One Protection Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the hide_notice() function in versions up to, and including, 1.5.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to dismiss notices.
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.
CWE-862: Missing Authorization
Security Optimizer <= 1.5.0 carries this weakness at hide_notice(), 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 Security Optimizer the fix is 1.5.1: builds <= 1.5.0 are affected, anything from 1.5.1 onward is not.
Remediation
Update to version 1.5.1, 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: Security Optimizer 1.5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Security Optimizer – The All-In-One Protection Plugin
- 9.8CVE-2022-0992: SiteGround Security <= 1.2.5 Authentication Bypass
CVE-2022-0992 - 8.1CVE-2022-0993: SiteGround Security Authorization Weakness
CVE-2022-0993 - 7.2CVE-2023-0234: SiteGround Security <= 1.3.0 SQL Injection
CVE-2023-0234 - 5.3CVE-2026-82228: Security Optimizer 2-Factor Authentication Bypass
CVE-2026-82228 - 5.3CVE-2026-13342: Security Optimizer IP Allowlist Bypass
CVE-2026-13342
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C