# CVE-2026-119303: NotificationX < 3.3.7 - Unauthenticated Settings Update and Email Sending via send-rating REST Route

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

The NotificationX  WordPress plugin before 3.3.7 does not perform any capability or nonce check on one of its REST routes, allowing unauthenticated users to update a NotificationX  WordPress plugin before 3.3.7 option and to repeatedly trigger emails sent through the site's own mail server.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / NotificationX: ≥ 0; < 3.3.7 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-862

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/0280952e-f388-44a3-a891-5855580a5f5b/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/0280952e-f388-44a3-a891-5855580a5f5b/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-119303; retrieved 2026-11-11; source updated 2026-11-11

Revision: 00fc50514f350c698e66f9693c32506b566a3cc13eb0198e2e87318034d33cd8

Canonical: https://y2.dev/cve/CVE-2026-119303

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.