Quick answers
- Is CVE-2026-7170 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7170 being exploited in the wild.
- How severe is CVE-2026-7170?
- Informational severity, published 28 September 2026.
- Which products and versions are affected?
- TPVEnlanube <UNKNOWN>.
- Is there a fix for CVE-2026-7170?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7170 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-7170?
- Check whether you run TPVEnlanube 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
Stored XSS vulnerability in TPVEnlanube affecting multiple administrative endpoints: vendor_store_name parameter in store.store_add, and user profile fields (Apellido 1, Nombre Completo) in user administration pages. The vulnerability requires prior authentication and affects CWE-79 unsanitized input handling. No patch is currently available.
Affected products
- TPVEnlanube TPVEnlanube <UNKNOWN>
Timeline
- 2026-09-28: disclosed
- 2026-09-28: advisory: INCIBE-2026-668