Gainsight Assist OAuth Call state get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Gainsight Assist. Affected by this issue is some unknown functionality of the component OAuth Call Handler. The manipulation of the argument state leads to use of get request method with sensitive query strings. This vulnerability is uniquely identified as CVE-2026-31381. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Gainsight Assist (affected version not known) and classified as problematic. This issue affects some unknown functionality of the component OAuth Call Handler. The manipulation of the argument state with an unknown input leads to a use of get request method with sensitive query strings vulnerability. Using CWE to declare the problem leads to CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. Impacted is confidentiality. The summary by CVE is:
An attacker can extract user email addresses (PII) exposed in base64 encoding via the state parameter in the OAuth callback URL.
The weakness was disclosed by Christopher O'Boyle. It is possible to read the advisory at rapid7.com. The identification of this vulnerability is CVE-2026-31381 since 03/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/26/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (rapid7): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/09/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
03/26/2026 VulDB entry last update
Sources
Advisory: rapid7.comResearcher: Christopher O'Boyle
Status: Not defined
CVE: CVE-2026-31381 (🔒)
GCVE (CVE): GCVE-0-2026-31381
GCVE (VulDB): GCVE-100-352067
Entry
Created: 03/20/2026 14:59Updated: 03/26/2026 18:09
Changes: 03/20/2026 14:59 (62), 03/26/2026 18:09 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.