dbcve.org
JetpackWordPress extension · Automattic

CVE-2024-10076

MEDIUM · 5.9 CVSS v3.1 Published 2025-05-15
Fix available
A fix is available. Upgrade to 3.4.8 / 13.8 or later.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Jetpack WordPress plugin before 13.8, Jetpack Boost WordPress plugin before 3.4.8 use regexes in the Site Accelerator features when switching image URLs to their CDN counterpart. Unfortunately, some of them may match patterns it shouldn’t, ultimately making it possible for contributor and above users to perform Stored XSS attacks

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jetpack and Jetpack Boost plugins contain flawed regex patterns in their Site Accelerator CDN image URL replacement feature. These regexes incorrectly match patterns beyond intended image URLs, allowing contributor-level or higher authenticated users to inject malicious scripts that execute when the CDN-modified content is rendered (Stored XSS).

MitigationUpdate Jetpack to version 13.8 or later and Jetpack Boost to version 3.4.8 or later to obtain the corrected regex patterns. Until patched, restrict contributor-level permissions and monitor for suspicious content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JetpackWordPress extension
Affected:< 13.8
Jetpack BoostWordPress extension
Affected:< 3.4.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Jetpack plugin is installed and identify its version
    Go to Plugins > Installed Plugins in WordPress admin, or check the version number in the Jetpack plugin header file (usually wp-content/plugins/jetpack/readme.txt or composer.json)
    Affected if Jetpack version is below 13.8
  2. Check if Jetpack Boost plugin is installed and identify its version
    Go to Plugins > Installed Plugins in WordPress admin, or check the version number in the Jetpack Boost plugin header file (usually wp-content/plugins/jetpack-boost/readme.txt or composer.json)
    Affected if Jetpack Boost version is below 3.4.8
  3. Verify if Jetpack Site Accelerator feature is enabled
    Navigate to Jetpack Settings in WordPress admin, look for the Site Accelerator (formerly Photon) setting under Performance and Speed settings, and confirm whether the CDN for images is turned on
    Affected if Jetpack Site Accelerator/CDN feature is enabled and Jetpack version is below 13.8
  4. Verify if Jetpack Boost Site Accelerator feature is enabled
    Navigate to Jetpack Boost settings in WordPress admin, check the 'Image CDN' or 'Site Accelerator' module is active
    Affected if Jetpack Boost Image CDN is enabled and Jetpack Boost version is below 3.4.8
  5. Review recent posts/pages for suspicious script injection in image-related content
    Search WordPress database or use a security plugin to scan post_content for unescaped script tags within img shortcodes or image URL attributes, particularly in content created by users with contributor or higher roles
    Affected if Malicious script tags are found in post content that would be processed by the CDN URL replacement

A user is affected if either Jetpack (< 13.8) or Jetpack Boost (< 3.4.8) is installed with its respective Site Accelerator or Image CDN feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.8 / 13.8 or later
Fixed in 3.4.813.8
Interim mitigation

Update Jetpack to version 13.8 or later and Jetpack Boost to version 3.4.8 or later to obtain the corrected regex patterns. Until patched, restrict contributor-level permissions and monitor for suspicious content.

Recommended fix Moderate confidence

Jetpack 13.8 and Jetpack Boost 3.4.8 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate Jetpack and check if the current version is below 13.8
  4. 4. If vulnerable, click 'Update Now' to update Jetpack to version 13.8 or later
  5. 5. Locate Jetpack Boost and check if the current version is below 3.4.8
  6. 6. If vulnerable, click 'Update Now' to update Jetpack Boost to version 3.4.8 or later
  7. 7. After updates, verify the Site Accelerator feature still functions correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jetpack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10076 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data