WordPress security changelog
MEDIUM CVE-2026-119059 Received

Content Egg – Affiliate Product Importer & Price Comparison: Unauthorized cross-post product updates

The Content Egg plugin for WordPress is vulnerable to unauthorized modification of data due to a missing per-post capability check on the ajaxUpdateProducts() function in versions up to, and including, 12.0.0. The handler verifies a static nonce ('contentegg_metabox') and the generic 'edit_posts' capability, but trusts the attacker-supplied $_POST['post_id'] verbatim and never calls current_user_can('edit_post', $post_id) — the per-object check that its sibling save_post handler saveMeta() correctly performs. This makes it possible for authenticated attackers, with contributor-level access and above, to modify Content Egg product data (_cegg_data_*) and update-timestamp post meta on arbitrary posts, including those owned by administrators. The structured affected range is <= 12.0.0.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Content Egg – Affiliate Product Importer & Price Comparison
Plugin slug
content-egg
Affected
<= 12.0.0
Safe version
See mitigation notes
Published
Oct 30, 2026
Weakness
CWE-862 — Missing Authorization

This CVE was published Oct 30, 2026 and is one of 8 known issues for this plugin.

What to do

Update, patch or deactivate.

Official author notes reviewed on 2026-10-30 through version 12.1.0 did not establish an exact fixed release for this CVE. Generic permissions do not identify AJAX cross-post product-update authorization. This archive’s uncertainty does not establish that the current release remains vulnerable. Limit access to the affected functionality until a matching fix can be verified. Official author notes: https://wordpress.org/plugins/content-egg/#developers.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Content Egg plugin for WordPress is vulnerable to unauthorized modification of data due to a missing per-post capability check on the ajaxUpdateProducts() function in versions up to, and including, 12.0.0. The handler verifies a static nonce ('contentegg_metabox') and the generic 'edit_posts' capability, but trusts the attacker-supplied $_POST['post_id'] verbatim and never calls current_user_can('edit_post', $post_id) — the per-object check that its sibling save_post handler saveMeta() correctly performs. This makes it possible for authenticated attackers, with contributor-level access and above, to modify Content Egg product data (_cegg_data_*) and update-timestamp post meta on arbitrary posts, including those owned by administrators.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources