Quick answers
- Is CVE-2026-14857 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14857 being exploited in the wild.
- How severe is CVE-2026-14857?
- Medium severity, with a CVSS score of 4.3, published 12 August 2026.
- Which products and versions are affected?
- WP Crowdfunding before 2.2.1.
- Is there a fix for CVE-2026-14857?
- A patch was published on 2026-08-12: Fixed in version 2.2.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14857 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14857?
- Check whether you run WP Crowdfunding 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 vulnerability is an Insecure Direct Object Reference (IDOR) in the campaign update functionality. The plugin's wpneo_update_status_save AJAX action does not properly validate campaign ownership before processing updates to campaign history metadata and sending notification emails to backers. An authenticated user with only Subscriber privileges can craft a POST request to wp-admin/admin-ajax.php with a nonce harvested from the public dashboard, substituting any campaign's post ID to modify its update history and trigger fraudulent notifications. The attacker's content is persisted in campaign meta and distributed to all backers via email, appearing to come from the legitimate campaign owner.
Affected products
- WP Crowdfunding WP Crowdfunding before 2.2.1
Timeline
- 2026-08-10: disclosed
- 2026-08-12: patched: Fixed in version 2.2.1