Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 11 May 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:v2board:v2board:*:*:*:*:*:*:*:* |
Sat, 02 May 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Token Exposure via GET Parameters in V2Board |
Fri, 01 May 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
V2board
V2board v2board |
|
| Vendors & Products |
V2board
V2board v2board |
Fri, 01 May 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-598 | |
| Metrics |
ssvc
|
Fri, 01 May 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Sensitive server_token exposed via GET parameter in V2Board thru 1.7.4. In app/Http/Controllers/Server/UniProxyController.php, the server authentication token is accepted via GET parameter transmission. The token appears in URLs such as /api/v1/server/UniProxy/user?token=SECRET, causing it to be recorded in web server access logs, browser history, HTTP Referer headers, and proxy/CDN logs. An attacker who gains access to any log source can extract the token and impersonate a proxy server node, potentially intercepting all user traffic. | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-05-01T19:46:01.535Z
Reserved: 2026-04-06T00:00:00.000Z
Link: CVE-2026-37504
Updated: 2026-05-01T19:39:51.275Z
Status : Analyzed
Published: 2026-05-01T16:16:30.633
Modified: 2026-05-11T19:25:20.300
Link: CVE-2026-37504
No data.
OpenCVE Enrichment
Updated: 2026-05-02T11:00:06Z