JetpackWordPress extension · Automattic
CVE-2023-47774
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 · uneditedImproper Restriction of Rendered UI Layers or Frames vulnerability in Automattic Jetpack allows Clickjacking.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 · high confidenceImproper Restriction of Rendered UI Layers or Frames vulnerability in Automattic Jetpack allows Clickjacking. The plugin fails to properly restrict how its UI can be embedded in frames, enabling attackers to overlay transparent elements and trick users into unintended actions.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Jetpack plugin is installedCheck the WordPress plugins directory or admin panel for the Jetpack plugin presenceAffected if Jetpack plugin is installed on the WordPress site
-
Determine installed Jetpack versionAccess WordPress admin > Plugins > Jetpack, or check the version in the plugin's main PHP file (jetpack/jetpack.php)Affected if Installed version is lower than 12.7
-
Check for clickjacking protection headersUse browser dev tools, curl, or an HTTP header checker to inspect responses from the Jetpack admin pages. Look for X-Frame-Options or Content-Security-Policy with frame-ancestors directiveAffected if Neither X-Frame-Options nor CSP frame-ancestors header is present on Jetpack admin pages
-
Test if site pages can be embedded in framesCreate a simple HTML page with an iframe src pointing to the target site. Load it in a browser and verify if the content renders within the frameAffected if The site loads successfully inside a frame, indicating missing frame restriction
A user is affected if Jetpack versions below 12.7 are installed AND the site allows embedding in frames without X-Frame-Options or CSP frame-ancestors protection.
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, which includes proper X-Frame-Options or Content-Security-Policy frame-ancestors headers to prevent clickjacking attacks.
Jetpack 12.7
- Update the Jetpack plugin to version 12.7 or later to resolve the clickjacking vulnerability.
- In WordPress admin dashboard, navigate to Plugins > Installed Plugins > Jetpack.
- If an update is available, click 'Update Now' to install version 12.7 or newer.
- Alternatively, update via wp-cli: wp plugin update jetpack
- Verify the update was successful by checking the Jetpack version in Plugins list.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jetpack
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47774 — 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-47774 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