CVE-2026-87850: Session Token Exposure via URL Query String in Axence nVision

Published Nov 18, 2026
·
Updated

nVision sends user's token via query parameters of GET requests. An attacker who obtains valid token can gain access to the victim's account and perform actions on their behalf.

This issue was fixed in version 18.

Affected Software

1 affected component
Axence nVision<18

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18

Event History

Nov 18, 2026
CVE Published
via MITRE·10:35 AM
Data Sourced
via MITRE·10:35 AM
DescriptionWeakness
Data Sourced
via NVD·11:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Users of Axence nVision versions before 18 are exposed because session tokens are sent in GET request query parameters. Anyone who obtains a valid token can access the associated account and act as that user.

2

What does an attacker need to exploit the issue?

The attacker needs to obtain a valid user's session token. The provided information does not describe a separate authentication bypass or other prerequisite.

3

What should organizations do?

Upgrade Axence nVision to version 18, where this issue is fixed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203