JetpackWordPress extension · Automattic
CVE-2023-47788
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 · uneditedMissing Authorization vulnerability in Automattic Jetpack.This issue affects Jetpack: from n/a before 12.7.
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 · moderate confidenceA missing authorization vulnerability exists in Automattic Jetpack plugin for WordPress. This access control flaw allows unauthenticated or unauthorized users to potentially access functionality or data they should not have permission to reach, prior to version 12.7.
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
< 12.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Jetpack versionLog into WordPress admin dashboard, navigate to Plugins section, locate Jetpack in the plugin list, and view the version number displayed. Alternatively, inspect the Jetpack plugin main file header (typically in /wp-content/plugins/jetpack/)Affected if The displayed version is lower than 12.7 (for example, 12.6, 12.5, etc.)
-
Verify Jetpack plugin statusConfirm that the Jetpack plugin is installed and active on the WordPress site. Check the Plugins > Installed Plugins page in WordPress adminAffected if Jetpack is installed and active with a version below 12.7
-
Confirm Jetpack version via plugin filesAccess the WordPress site files via FTP or file manager, locate the jetpack/jetpack.php file, and read the Version header from the file comment blockAffected if The Version header in jetpack.php shows a version number less than 12.7
The environment is affected if the installed Jetpack plugin version is below 12.7, regardless of specific configuration, since the missing authorization vulnerability exists in the plugin core for those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.7
Update Jetpack to version 12.7 or later to patch the missing authorization vulnerability.
Jetpack 12.7
- 1. Backup your WordPress site database and files before making any changes
- 2. Update Jetpack plugin to version 12.7 or later through WordPress admin dashboard (Plugins > Updates) or via wp-cli: wp plugin update jetpack
- 3. Verify the update was successful by checking Plugins > Installed Plugins > Jetpack version number
- 4. Test that Jetpack functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jetpack
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47788 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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