CVE-2026-37504: V2Board thru · Sensitive server_token exposed via GET parameter
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 27 Oct 2026, 00:46 UTC
CVSS:3.1/AC:H/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:RExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubv2board/v2boardpkg:github/v2board/v2boardOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability arises from transmitting sensitive tokens via GET parameters, it is recommended to avoid passing authentication tokens in URLs. Instead, use more secure methods such as HTTP headers or POST parameters. Additionally, restrict access to logs that may contain sensitive tokens and consider rotating tokens if exposure is suspected. Monitor vendor advisories for any official fixes or updates.
Description
V2Board versions through 1.7.4 expose a sensitive server authentication token via a GET parameter in the UniProxyController. This token appears in URLs and can be logged in various places such as web server logs, browser history, and proxy/CDN logs. An attacker with access to these logs could extract the token and impersonate a proxy server node, potentially intercepting user traffic.