PatchTheCVEjetpack vulnerabilities and fixes
Recent CVEs affecting jetpack, with upgrade or downgrade steps. 5 tracked.
jetpack has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-01-13. Highest priority: CVE-2024-9926 (score 38/100).
- CVE-2024-9926 MEDIUM 4.3 UPGRADE The Jetpack WordPress plugin does not have proper authorisation in one of its REST endpoint, allowing any auth
- CVE-2024-10858 MEDIUM 6.1 UPGRADE The Jetpack WordPress plugin before 14.1 does not properly checks the postmessage origin in its 13.x versions
- CVE-2024-10076 MEDIUM 5.9 UPGRADE UPGRADE The Jetpack WordPress plugin before 13.8, Jetpack Boost WordPress plugin before 3.4.8 use regexes in the Sit
- CVE-2024-10075 MEDIUM 5.6 UPGRADE The Jetpack WordPress plugin before 13.8 does not ensure that the post created by the Contact Form is only ac
- CVE-2023-54332 MEDIUM 6.1 DOWNGRADE Jetpack 11.4 contains a cross-site scripting vulnerability in the contact form module that allows attackers to
FAQ
How do I fix jetpack vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jetpack being exploited right now?
None of the tracked jetpack CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jetpack CVE should I patch first?
CVE-2024-9926 currently ranks highest (38/100): The Jetpack WordPress plugin does not have proper authorisation in one of its REST endpoint, allowing any auth.