CVE-2026-37504: Sensitive server_token exposed via GET parameter in V2Board thru 1.7.4

Q: How do I fix CVE-2026-37504?

v2board: upgrade to newer than 1.7.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-37504 being exploited?

CVE-2026-37504 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-37504 affect?

CVE-2026-37504 affects v2board. Severity is medium (CVSS 5.3). 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 /ap

Q: How urgent is CVE-2026-37504?

Priority 29/100. Public exploit reference

Routine

MEDIUM 5.3UPGRADE

CVE-2026-37504 is a medium-severity flaw (CVSS 5.3) affecting v2board. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-598
Published	2026-05-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: v2board

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-01 16:16 UTCPublished CVE record published
2026-06-17 10:41 UTCUpdated Record last modified

v2board v2board UPGRADE

Affected: <= 1.7.4

Fixed in: newer than 1.7.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy v2board || rpm -q v2board || v2board --version

2. UPGRADE to newer than 1.7.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade v2board

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade v2board

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-37504?

v2board: upgrade to newer than 1.7.4. Exact commands for each OS are on this page.

Is CVE-2026-37504 being exploited?

CVE-2026-37504 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-37504 affect?

CVE-2026-37504 affects v2board. Severity is medium (CVSS 5.3). 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 /ap

How urgent is CVE-2026-37504?

Priority 29/100. Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2026-37505 MEDIUM 4.9 UPGRADE SQL Injection via ORDER BY clause in V2Board thru 1.7.4
CVE-2026-37503 MEDIUM 6.9 UPGRADE Cross-Site Scripting (XSS) in V2Board thru 1.7.4

References

← Back to latest CVEs