CVE-2024-31842: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
AI-suggested
1. Immediately audit all token handling mechanisms in Italtel Embrace and remove access tokens from GET request URLs. 2. Transition token transmission to POST requests or secure HTTP headers to prevent exposure in URLs and referer headers. 3. Implement short-lived, single-use tokens to limit the window of exploitation if tokens are leaked. 4. Enforce secure cookie attributes such as HttpOnly, Secure, and SameSite to protect session tokens. 5. Monitor web server logs and referer headers for suspicious token leakage or unauthorized access attempts. 6. Educate users and administrators about the risks of sharing URLs containing sensitive tokens. 7. If possible, apply application-layer filters to strip tokens from referer headers before requests leave the network. 8. Engage with Italtel support or vendors for patches or updates addressing this vulnerability. 9. Conduct penetration testing focusing on session management and token exposure to verify mitigation effectiveness.
Description
An issue was discovered in Italtel Embrace 1.6.4. The web application inserts the access token of an authenticated user inside GET requests. The query string for the URL could be saved in the browser's history, passed through Referers to other web sites, stored in web logs, or otherwise recorded in other sources. If the query string contains sensitive information such as session identifiers, then attackers can use this information to launch further attacks. Because the access token in sent in GET requests, this vulnerability could lead to complete account takeover.