WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager < 2.4.0 - Unauthenticated Snippet Safe Mode Bypass
Strategic Overview
- Status
- Patched in 2.4.0
- Affected Version
< 2.4.0- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-101301
At a glance
CVE-2026-101301 is a high-severity Missing Authorization vulnerability in the WPCode WordPress plugin, affecting versions < 2.4.0. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.4.0; sites on affected versions should update now. Disclosed October 2026, reported by Kenny of Greenhat Security.
Vulnerability Overview
The WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager plugin for WordPress is vulnerable to Bypass Vulnerability in all versions up to 2.4.0. This is due to insufficient verification of the login page check in wpcode_is_wplogin(), allowing any unauthenticated request with the safe mode parameter to bypass snippet execution. This makes it possible for unauthenticated attackers to disable all automatically inserted snippets for their own requests by triggering safe mode without authentication.
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
WPCode < 2.4.0 carries this weakness at wpcode_is_wplogin(), and reaching it takes no account at all. 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 WPCode the fix is 2.4.0: builds < 2.4.0 are affected, anything from 2.4.0 onward is not.
Remediation
Update to version 2.4.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPCode 2.4.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WPCode – Insert Headers and Footers + Custom Code Snippets – WordPress Code Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C