CVE-2026-119751 · Package
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Content Egg WordPress plugin before 12.1.0 that store unpublished posts with product content. The exposed route is reachable without logging in, so any WordPress site with this plugin and draft or private posts containing Content Egg blocks is in scope. Sites without the plugin or on 12.1.0 or later are not affected.
Not affected if plugin-not-installed, version-12.1.0-or-later
Who cares content-egg, self-hosted, wordpress
wp-content/plugins/content-egg//wp-json/content-egg/v1/render-blocks on the site and see whether it responds to unauthenticated POST requests12.1.0 or laterContent 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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.