NotificationX Pro <= 3.1.4 - Unauthenticated Stored Cross-Site Scripting

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps WPDeveloper/NotificationX Pro (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for WPDeveloper/NotificationX Pro.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 25, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 25, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 25, 2026

Sources and claim methodology

• Source referencepatchstack.com
• Source referencewordfence.com

Related CVEs

• hbs vulnerable to XSS via registerAsyncHelper output-escaping bypassAlso CWE-79
• MetForm <= 4.1.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'mf_form_id' Widget SettingAlso CWE-79
• Forminator Forms <= 1.57.0.2 - Unauthenticated Stored Cross-Site Scripting via Radio Field (Save and Continue Draft)Also CWE-79
• Forminator Forms <= 1.57.0 - Unauthenticated DOM-Based Cross-Site Scripting via 'error_description' ParameterAlso CWE-79
• TranslatePress <= 3.2.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Approved Comment Body in Translation EditorAlso CWE-79
• Reflected XSS in AshAuthentication confirmation and magic link interaction formsAlso CWE-79