CVE-2026-119059
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
The Content Egg plugin for WordPress in versions up to and including 12.0.0 lacks a per-post capability check in the ajaxUpdateProducts() function. An authenticated attacker with contributor-level access or above can modify Content Egg product data and update-timestamp post meta on arbitrary posts, including those owned by administrators.
Risk Assessment
Unauthorized modification of data on arbitrary posts can lead to content tampering, product data manipulation, and integrity violations of the site.
Recommendation
Update the Content Egg plugin to a version later than 12.0.0. Until then, restrict contributor roles and monitor post metadata changes.
Other vulnerabilities in Content Egg
See all- CVE-2026-96832High
PHP Object Injection vulnerability in Content Egg plugin up to version 6.3.1, exploitable by users with Shop manager role. May lead to execution of malicious PHP objects.
- CVE-2026-119087Medium
The Content Egg plugin for WordPress in versions up to and including 12.0.0 does not properly verify that a user is authorized to perform an action. An authenticated attacker with author-level access or above can create posts attributed to another user's account, typically an administrator, by supplying an admin-owned preset_id.
- CVE-2026-15979High
The Content Egg plugin for WordPress is vulnerable to Arbitrary File Deletion via Path Traversal in versions up to and including 11.3.0. Insufficient validation of the 'img_file' field allows authenticated attackers with author-level access or above to delete arbitrary files on the server.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS