Skip to main content
VulnerabilityPublished

CVE-2026-37503: V2Board thru · Cross-Site Scripting (XSS)

Source GCVE Database

0
Authoritative record:CVE-2026-37503· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 27 Oct 2026, 00:45 UTC

CVSS 3.1 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:H/S:C/UI:R

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubv2board/v2boardpkg:github/v2board/v2boardOther threatsAffected
  • <=1.7.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict administrative access to trusted users only and monitor for suspicious activity related to theme configuration changes. Avoid exposing the saveThemeConfig API to untrusted administrators if possible.

Description

CVE-2026-37503 is a Cross-Site Scripting (XSS) vulnerability in V2Board versions through 1.7.4. It arises from the custom_html field in theme configuration being rendered without escaping in the dashboard template. An administrator can inject arbitrary JavaScript via the saveThemeConfig API, which executes in the browsers of all site visitors. This can lead to cookie theft, session hijacking, or phishing attacks.

References

Community reviews

Loading reviews…