Quick answers
- Is CVE-2026-19434 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19434 being exploited in the wild.
- How severe is CVE-2026-19434?
- Informational severity, with a CVSS score of 6.5, published 11 August 2026.
- Which products and versions are affected?
- maalfer Pentestify before 2.3.1.
- Is there a fix for CVE-2026-19434?
- A patch was published on 2026-07-17: Fix committed; v2.3.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19434 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-19434?
- Check whether anything you run is named in the advisory. 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 a stored cross-site scripting (XSS) flaw in the finding renderer component. The backend accepted the severity field without validation, and the frontend interpolated it unescaped into HTML class and style attributes (e.g., `severity-<x>` and `var(--severity-<x>)`). An authenticated attacker could break the attribute boundary using `">` and inject an `<img onerror>` tag or similar payload to execute arbitrary JavaScript in the context of the application. The fix, released in v2.3.2, implements a whitelist of permitted severity values (crit, high, med, low, info) on both backend and frontend, and sanitizes output in all rendering sinks.
Affected products
- maalfer Pentestify before 2.3.1
Timeline
- 2026-08-11: disclosed: CVE-2026-19434 published
- 2026-07-17: patched: Fix committed; v2.3.2 released