Skip to main content
VulnerabilityPublished

CVE-2026-68551: teelur budget-board · Improper Authentication

Affects teelur budget-boardSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 3.6.2 soon.

Data as of 13 Nov 2026, 20:18 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.3
Patch
Available – fixed in 3.6.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 13 Nov 2026.

What to do

Upgrade teelur budget-board to 3.6.2.

Affected software

ProductAffectedFixed in
teelurbudget-boardAffected
  • <3.6.2
Fixed in
  • 3.6.2

AI-suggested

Upgrade Budget Board to version 3.6.2 or later, where the OIDC login flow properly verifies the email_verified claim to ensure email ownership before signing in users. No other mitigation is required as the issue is fixed in this version.

Description

Budget Board versions prior to 3.6.2 have an improper authentication vulnerability in their OIDC login flow. The app signs into existing local accounts based solely on the email address from the identity provider's token without verifying the email ownership via the email_verified claim. This flaw allows an attacker to register with a victim's email on the OIDC provider and gain unauthorized access to the victim's Budget Board account, including sensitive linked bank data. The issue is fixed in version 3.6.2.

References

Community reviews

Loading reviews…