CVE-2025-40646: Exposure of sensitive information in Viday
Exposure of sensitive information in Viday. This vulnerability could allow an attacker to obtain sensitive information about customers by intercepting HTTP requests and searching for the JWT containing sensitive user information in the JWT payload.
Security readout for executives and security teams
Plain-English summary
CVE-2025-40646 is a sensitive information exposure issue in ViDay. The source says an attacker could intercept HTTP requests and find a JWT whose payload contains sensitive customer information. The business concern is confidentiality, not service disruption or data modification.
Executive priority
Treat this as a confidentiality risk requiring timely validation. It is not currently evidenced as exploited, but customer data exposure through tokens can create privacy, trust, and notification concerns if confirmed.
Technical view
The reported weakness maps to CWE-200. The CVSS 4.0 score is 5.9, with adjacent attack vector, high attack complexity, no privileges required, passive user interaction, and high vulnerable-system confidentiality impact. Integrity and availability impacts are not reported.
Likely exposure
Organizations using ViDay should assess exposure, especially where ViDay traffic or integrations can traverse plaintext HTTP or untrusted adjacent networks. The bundle lists ViDay as affected, but version and remediation details are limited.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as KEV. Exploitation depends on intercepting HTTP requests and locating sensitive data inside JWT payloads, according to the description.
Researcher notes
Evidence is narrow: the bundle gives the vulnerability description, CVSS, CWE-200, ViDay as affected, and one INCIBE advisory. It does not provide exploit details, patch identifiers, or detailed affected-version boundaries.
Mitigation direction
Check INCIBE or vendor guidance for fixed versions or official configuration advice.
Eliminate plaintext HTTP for ViDay traffic where configuration allows.
Restrict ViDay access to trusted networks until token transport is confirmed.
Review JWT contents and remove customer-sensitive fields where administratively possible.
Rotate potentially exposed tokens if interception is suspected.
Validation and detection
Inventory ViDay deployments and confirm where the product is used.
Verify whether ViDay client or integration traffic uses HTTP.
Inspect controlled JWT samples for customer-sensitive payload fields.
Review proxy or gateway logs for plaintext authentication-token traffic.
Confirm any vendor-provided fix or advisory has been applied.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.