Quick answers
- Is CVE-2026-119303 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119303 being exploited in the wild.
- How severe is CVE-2026-119303?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- NotificationX before 3.3.7.
- Is there a fix for CVE-2026-119303?
- Yes: fixed in 3.3.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119303 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-119303?
- Check whether you run NotificationX 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.
How to fix
- Fixed in: 3.3.7
Technical details
The plugin fails to implement capability and nonce checks on its send-rating REST route, allowing unauthenticated access to modify plugin options and send emails. This is a missing authorization vulnerability (CWE-862) requiring only network access to exploit. The vulnerability allows attackers to abuse the site's email infrastructure without authentication.
Affected products
- NotificationX NotificationX before 3.3.7
Timeline
- 2026-11-09: disclosed
- 2026-11-09: patched: Fixed version 3.3.7 available