---
id: "CVE-2026-119751"
kind: "vulnerability"
aliases: ["CVE-2026-119751"]
title: "WordPress Content Egg plugin: unauthenticated leak of unpublished post data"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["content-egg", "package", "self-hosted", "wordpress"]
not_affected_if: ["plugin-not-installed", "version-12.1.0-or-later"]
published_at: "2026-11-05T16:17:40+00:00"
first_seen_at: "2026-11-05T16:40:01+00:00"
updated_at: "2026-11-05T16:41:36+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119751", "first_seen_at": "2026-11-05T16:40:01+00:00"}]
exploit_sources: []
---

# WordPress Content Egg plugin: unauthenticated leak of unpublished post data

The Content Egg plugin for WordPress before 12.1.0 has a REST route whose permission check passes when no nonce header is sent, so anyone can call it. Unauthenticated attackers can read product titles, affiliate URLs, merchant details and descriptions from draft, pending, scheduled or private posts.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Content Egg plugin version in the WordPress admin Plugins page or in `wp-content/plugins/content-egg/`
- Look for the route `/wp-json/content-egg/v1/render-blocks` on the site and see whether it responds to unauthenticated POST requests

## Fix

- Content Egg: move to `12.1.0` or later

## Timeline

- 2026-11-05T16:40:01+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119751

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/content-egg-wordpress-plugin-unauthenticated-information-disclosure-via-render-blocks

## From the sources

Content Egg plugin for WordPress before 12.1.0 contains a broken access control vulnerability that allows unauthenticated attackers to retrieve Content Egg product data from unpublished posts by calling the REST route POST /wp-json/content-egg/v1/render-blocks, whose permission_check() improperly returns true when no X-WP-Nonce header is supplied. Attackers can supply the post_id and module id of a draft, pending, scheduled, or private post to handle_render(), which lacks a publish-status check, to disclose product titles, destination and affiliate URLs, merchant or domain information, and descriptions.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_