Head, Footer and Post Injections <= 3.3.0 - Authenticated (Administrator+) PHP Code Injection in Multisite Environments
Strategic Overview
- Status
- Patched in 3.3.1
- Affected Plugin
- Head, Footer and Post Injections
- Affected Version
<= 3.3.0- CVSS
- 4.1Medium
- Weakness type
- CWE-94 · Improper Control of Generation of Code ('Code Injection')
- CVE
CVE-2024-13900
At a glance
CVE-2024-13900 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Head, Footer and Post Injections WordPress plugin, affecting versions <= 3.3.0. It carries a CVSS score of 4.1 (reachable over the network). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 3.3.1; sites on affected versions should update now. Disclosed February 2025, reported by Francesco Carlucci.
Vulnerability Overview
The Head, Footer and Post Injections plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 3.3.0. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject PHP Code in multisite environments.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-94: Improper Control of Generation of Code ('Code Injection')
Reaching this weakness in Head, Footer and Post Injections <= 3.3.0 takes an account at Administrator level or above. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.
The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Head, Footer and Post Injections the fix is 3.3.1: builds <= 3.3.0 are affected, anything from 3.3.1 onward is not.
Remediation
Update to version 3.3.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Head, Footer and Post Injections 3.3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C