Quick answers
- Is CVE-2026-75905 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75905 being exploited in the wild.
- How severe is CVE-2026-75905?
- Medium severity, with a CVSS score of 4.3, published 9 September 2026.
- Which products and versions are affected?
- WP Recipe Maker up to and including 10.8.0.
- Is there a fix for CVE-2026-75905?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75905 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75905?
- Check whether you run WP Recipe Maker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WP Recipe Maker plugin fails to properly verify user authorization when handling recipe updates, specifically when modifying the post_author and post_status fields. An authenticated attacker with contributor-level access or above can exploit this vulnerability via direct API calls or form submissions to overwrite the post_author field with their own user ID (if the 'recipe_use_author' setting is 'parent') and change the post_status to draft or pending. The vulnerability is accessible to any authenticated user at the contributor level or above and requires no additional user interaction. An attacker can achieve unauthorized ownership transfer and unpublishing of administrator-created recipes, disrupting content and potentially enabling further malicious actions. Patches are available in versions after 10.8.0.
Affected products
- WP Recipe Maker WP Recipe Maker up to and including 10.8.0
Timeline
- 2026-09-09: disclosed