Jetpack < 13.9.1 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 10.0.2
- Affected Plugin
- Jetpack – WP Security, Backup, Speed, & Growth
- Affected Version
3.9 – 13.9 · 101 branches- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-9926
At a glance
CVE-2024-9926 is a medium-severity Missing Authorization vulnerability in the Jetpack WordPress plugin, affecting versions 3.9 – 13.9 · 101 branches. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 10.0.2; sites on affected versions should update now. Disclosed October 2024.
Vulnerability Overview
The Jetpack – WP Security, Backup, Speed, & Growth plugin for WordPress is vulnerable to unauthorized access of data due to missing capability checks in the Contact_Form_Endpoint class in various versions version up to, but not including, 13.9.1. This makes it possible for authenticated attackers, with subscriber-level access and above, to read all Jetpack form submissions on the site.
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
Reaching this weakness in Jetpack 3.9 – 13.9 · 101 branches takes an account at Subscriber level or above. 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 Jetpack the fix is 10.0.2: builds 3.9 – 13.9 · 101 branches are affected, anything from 10.0.2 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 10.0.2, 10.1.2, 10.2.3, 10.3.2, 10.4.2, 10.5.3, 10.6.2, 10.7.2, 10.8.2, 10.9.3, 11.0.2, 11.1.4, 11.2.2, 11.3.4, 11.4.2, 11.5.3, 11.6.2, 11.7.3, 11.8.6, 11.9.3, 12.0.2, 12.1.2, 12.2.2, 12.3.1, 12.4.1, 12.5.1, 12.6.3, 12.7.2, 12.8.2, 12.9.4, 13.0.1, 13.1.4, 13.2.3, 13.3.2, 13.4.4, 13.5.1, 13.6.1, 13.7.1, 13.8.2, 13.9.1, 3.9.10, 4.0.7, 4.1.4, 4.2.5, 4.3.5, 4.4.5, 4.5.3, 4.6.3, 4.7.4, 4.8.5, 4.9.3, 5.0.3, 5.1.4, 5.2.5, 5.3.4, 5.4.4, 5.5.5, 5.6.5, 5.7.5, 5.8.4, 5.9.4, 6.0.4, 6.1.5, 6.2.5, 6.3.7, 6.4.6, 6.5.4, 6.6.5, 6.7.4, 6.8.5, 6.9.4, 7.0.5, 7.1.5, 7.2.5, 7.3.5, 7.4.5, 7.5.7, 7.6.4, 7.7.6, 7.8.4, 7.9.4, 8.0.3, 8.1.4, 8.2.6, 8.3.3, 8.4.5, 8.5.3, 8.6.4, 8.7.4, 8.8.5, 8.9.4, 9.0.5, 9.1.3, 9.2.4, 9.3.5, 9.4.4, 9.5.5, 9.6.4, 9.7.3, 9.8.3, 9.9.3
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: Jetpack 10.0.2 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 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-2024-10075: Jetpack <= 13.7 Arbitrary Block & Shortcode Execution
CVE-2024-10075 - 6.5CVE-2023-2996: Jetpack <= 12.1 Arbitrary File Manipulation
CVE-2023-2996
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C