Skip to main content
Menu
CVEs

CVE

CBoard missing authorization in admin and dashboard endpoints

CVE-2026-130073

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 7bd8180d8423a36b29a803433078bd66f94a81ed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. CBoard builds before commit 7bd8180

Published
Last modified
Reference
Last checked
15/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

TuiQiao's CBoard has a missing authorization flaw that lets any logged-in user reach admin functions, because some admin and dashboard controller methods skip role checks. Attackers can reach it remotely over the network with a low-privilege account to read query configurations and delete user accounts, including the administrator's.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

CBoard before commit 7bd8180 contains a missing authorization vulnerability that allows any authenticated user to reach admin functions because AdminController and DashboardController methods bypass AOP role checks. Attackers with no role grants can call deleteUser, deleteRole, getUserList, getAllWidgetList and getAllDatasetList to read query configurations and delete accounts including the administrator.

Who should check

Teams running TuiQiao CBoard builds older than commit 7bd8180, especially instances with multiple user accounts; any authenticated user can reach admin functions.

“CBoard before commit 7bd8180”

vulncheck.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    CBoard builds before commit 7bd8180
  • Upgrade to a fixed version: 7bd8180d8423a36b29a803433078bd66f94a81ed.

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-130073 (CBoard before commit 7bd8180 Missing Authorization in Admin and Dashboard Endpoints), 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-130073 (entry last updated 2026-11-16):
Affected:
- TuiQiao CBoard: version range not reported
Fixed versions: 7bd8180d8423a36b29a803433078bd66f94a81ed.
Conditions (all must be true for the bug to be hit):
- CBoard builds before commit 7bd8180 (source: https://www.vulncheck.com/advisories/cboard-before-commit-7bd8180-missing-authorization-in-admin-and-dashboard-endpoints)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130073 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130073 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/TuiQiao/CBoard/commit/7bd8180d8423a36b29a803433078bd66f94a81ed
- https://github.com/TuiQiao/CBoard/issues/740
- https://github.com/TuiQiao/CBoard/blob/046914c785eca1c1f91a8887ce36f1c2b34f25f6/src/main/java/org/cboard/controller/AdminController.java#L72-L98
- https://github.com/TuiQiao/CBoard/blob/046914c785eca1c1f91a8887ce36f1c2b34f25f6/src/main/java/org/cboard/services/role/ConfigRuleService.java#L135-L158
- https://www.vulncheck.com/advisories/cboard-before-commit-7bd8180-missing-authorization-in-admin-and-dashboard-endpoints
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-130073
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-130073"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • TuiQiao CBoard

    Version range not reported

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Report
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130073

Is CVE-2026-130073 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. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Any signed-in user of CBoard can read query configurations, list users, delete user accounts (including the administrator), and delete roles, because the admin and dashboard endpoints do not check authorization.Source: vulncheck.com

Am I affected, and how do I check?

CBoard builds before commit 7bd8180 are affected. The facts do not list version numbers, so compare the build you run against that commit.Source: vulncheck.com

How do I fix CVE-2026-130073?

Update CBoard to commit 7bd8180d8423a36b29a803433078bd66f94a81ed or later.Source: vulncheck.com