Customer data disclosure via sensitive JWT payloads
Published Oct 2, 2025 · Updated Oct 2, 2025
Sensitive information exposure in ViDay allows physically proximate attackers to read customer data in intercepted HTTP traffic. ViDay places sensitive user information inside JWT payloads carried by HTTP requests, so captured traffic exposes the encoded claims after decoding. Passive access to customer network traffic is required; the published scope covers all versions and reports customer-data disclosure only.
Summary
What happened
Sensitive information exposure in ViDay allows physically proximate attackers to read customer data in intercepted HTTP traffic. ViDay places sensitive user information inside JWT payloads carried by HTTP requests, so captured traffic exposes the encoded claims after decoding. Passive access to customer network traffic is required; the published scope covers all versions and reports customer-data disclosure only.
The record
- CVE
- CVE-2025-40646
- Published
- Oct 2, 2025
- Updated
- Oct 2, 2025
- Vendor
- ViDay
- Product
- ViDay
- Classifications
- CWE-200, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2025CVE publishedPublication date reported by the CVE source.
- Oct 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all versions
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo