How to Fix CVE-2026-37505: n/a (Bundle Sibling)
By Sai Kiran Pandrala
Last verified: 2026-05-25
CVE-2026-37505 is a sibling vulnerability in the same vendor advisory as CVE-2026-37503. Applying the patched build named in the primary write-up closes this CVE as well.
| Severity | CVSS 4.9 - Medium |
|---|---|
| Actively exploited? | Not currently in CISA KEV |
| Affected | Same as the bundle - see CVE-2026-37503 |
| Fixed in | Same patched build as CVE-2026-37503 (See vendor advisory) |
| Type (CWE) | n/a |
What's different about CVE-2026-37505?
SQL Injection via ORDER BY clause in V2Board thru 1.7.4. In app/Http/Controllers/Admin/UserController.php, the sort parameter from user input is passed directly to User::orderBy($sort, $sortType) without validation. An authenticated admin can sort users by any database column including password, remember_token, and other sensitive fields, enabling information disclosure through ordering analysis.
The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.
How to fix CVE-2026-37505
Apply the patched build per the primary write-up: How to Fix CVE-2026-37503.
The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.
Frequently asked questions
Is CVE-2026-37505 fixed by the same patch as CVE-2026-37503?
Yes. CVE-2026-37505 ships in the same vendor advisory as CVE-2026-37503. Applying the patched build named in the primary write-up closes both.
What is the CVSS score for CVE-2026-37505?
The CVSS base score is 4.9 (Medium).
Is it being exploited?
It is not currently listed in CISA KEV.
References
- Official vendor advisory: https://github.com/v2board/v2board
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-37505
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-37503
*Part of the n/a bundle. Full procedure at CVE-2026-37503.*