Jetpack <= 13.7 - Unauthenticated Arbitrary Block & Shortcode Execution
Strategic Overview
- Status
- Patched in 13.8
- Affected Plugin
- Jetpack – WP Security, Backup, Speed, & Growth
- Affected Version
<= 13.7- CVSS
- 6.5Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-10075
At a glance
CVE-2024-10075 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Jetpack WordPress plugin, affecting versions <= 13.7. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 13.8; sites on affected versions should update now. Disclosed October 2024, reported by Marc-Alexandre Montpas.
Vulnerability Overview
The The Jetpack – WP Security, Backup, Speed, & Growth plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 13.7. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Jetpack <= 13.7 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Jetpack the fix is 13.8: builds <= 13.7 are affected, anything from 13.8 onward is not.
Remediation
Update to version 13.8, 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: Jetpack 13.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Jetpack – WP Security, Backup, Speed, & Growth
- 9.8Jetpack – WP Security, Backup, Speed, & Growth < 4.2 Timing Attack
- 9.6Jetpack – WP Security, Backup, Speed, & Growth < 4.2 CSV Injection
- 7.2Jetpack 12.0 - 16.1.2 PHP Object Injection
- 7.2Jetpack <= 3.7.1 Stored Cross-Site Scripting
- 7.2Jetpack <= 3.5.2 Cross-Site Scripting
- 6.6Jetpack PHP Object Injection
- 6.5CVE-2023-2996: Jetpack <= 12.1 Arbitrary File Manipulation
CVE-2023-2996 - 6.4CVE-2024-10076: Jetpack & Jetpack Boost <= 3.4.7 - Authenticated
CVE-2024-10076
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C