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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
keywordrush:content egg – affiliate product importer & price comparison
References 6
https://plugins.trac.wordpress.org/browser/content-egg/tags/12.0.0/application/…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/content-egg/tags/12.0.0/application/…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/content-egg/tags/12.0.0/application/…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/content-egg/tags/12.0.0/application/…
security@wordfence.com
https://plugins.trac.wordpress.org/changeset?reponame=&old=3773366%40content-eg…
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/id/bc503fac-1ae6-400a-b1…
security@wordfence.com