CVE
Budget Board account takeover via unverified email in OIDC login
Only affects Budget Board instances with OIDC login enabled and pointed at an identity provider that lets users claim an email address without proving ownership. Fixed in 3.6.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.6.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.6.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.28% · 20th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 40/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
Budget Board, a personal budgeting app, can let an attacker sign into a victim's existing account through its OIDC login flow, which matches accounts by email address without checking that the address is verified. An attacker can do this remotely without logging in, provided the configured identity provider lets users register or display an email address they have not proven they own, and the attacker gets access to the victim's linked bank data.
Original description
Budget Board is an app for tracking monthly spending and working towards financial goals. Prior to version 3.6.2, Budget Board's OIDC login flow finds and signs into an existing local account purely by matching the email address asserted in the identity provider's token - it never checks the standard email_verified claim. If the configured OIDC provider ever allows a user to register or display an email address without proving they own it , an attacker can register there using a victim's email and get signed into the victim's existing Budget Board account - including all their linked bank data. This issue has been patched in version 3.6.2.
Who should check
Teams running Budget Board (BudgetBoard.WebAPI) with OIDC login enabled against a self-hosted or open-registration identity provider that may not verify email addresses.
“Budget Board's OIDC login flow finds and signs into an existing local account purely by matching the email address”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.6.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-68551 (Budget Board's OIDC login links to an existing local account by email alone, with no email_verified check, enabling account takeover of…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-68551 (entry last updated 2026-11-13):
Affected:
- teelur budget-board: fixed in 3.6.2
Fixed versions: 3.6.2.
Conditions (all must be true for the bug to be hit):
- OIDC login is enabled and pointed at an identity provider (source: https://github.com/teelur/budget-board/security/advisories/GHSA-576g-r8m3-q9vp)
- The configured OIDC provider lets a user register or display an email address without proving ownership of it (source: https://github.com/teelur/budget-board/security/advisories/GHSA-576g-r8m3-q9vp)
- The victim has an existing local Budget Board account with the same email address (source: https://github.com/teelur/budget-board/security/advisories/GHSA-576g-r8m3-q9vp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-68551 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68551 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/teelur/budget-board/security/advisories/GHSA-576g-r8m3-q9vp
- https://github.com/teelur/budget-board/pull/956
- https://github.com/teelur/budget-board/commit/8c050368e6a01c72f41ab39be913fbf95f1cb253
- https://github.com/teelur/budget-board/releases/tag/v3.6.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-68551
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68551"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- teelur budget-board
fixed in 3.6.2
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-68551
Is CVE-2026-68551 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
OIDC login signs a person into an existing local Budget Board account by matching only the email address, without checking that the email is verified. If the identity provider lets someone register or display an email they do not own, that person can be signed into the victim's account, gaining full access to linked bank accounts, balances, transactions and budgets, and the ability to modify or delete that data.Source: github.com
Which versions are affected by CVE-2026-68551?
budget-board: before 3.6.2.Source: cve.now feed data
Am I affected, and how do I check?
Affected setups have OIDC login enabled and pointed at an identity provider that can let a user register or display an email address without proving ownership, and the account holder has a local Budget Board account with that same email. Versions before 3.6.2 are in the affected range, so check the installed Budget Board version and whether OIDC login is enabled in the instance settings.Source: github.com
How do I fix CVE-2026-68551?
Upgrade Budget Board to 3.6.2 or later, which is the fixed version listed for this vulnerability.Source: github.com