Vulnerability in Lumiverse (CVE-2026-44443)
Summary
Vulnerability in Lumiverse (CVE-2026-44443). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/auth/sign-up/email. Mitigation: upgrade to 0.9.7 or later.
Original description
The description as published by the source.
Lumiverse is a full-featured AI chat application. Prior to 0.9.7, consumeNonce() only checks that the module-level variable is set and unexpired. It does not validate any value from the incoming HTTP request or bind the nonce to the admin's session. If the admin's auth.api.signUpEmail() call fails before the before hook fires (e.g. BetterAuth rejects a duplicate email at the validation layer), the nonce is set but never consumed. Any POST /api/auth/sign-up/email request that arrives during the remaining window registers successfully regardless of who sent it. An attacker who can observe or predict when the admin is creating users (must be a dupplicate user) can race the 10-second window to register an unauthorized account. This vulnerability is fixed in 0.9.7.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44443 has been found in Lumiverse.
Attackers can target a specific entry point like POST /api/auth/sign-up/email over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade Lumiverse to 0.9.7 or later.
If unsure, ask your IT team or search "Lumiverse CVE-2026-44443" on the vendor's site.
CVE-2026-44443 (Lumiverse) — CWE-362 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/auth/sign-up/email
Patched: 0.9.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in Lumiverse. Attackers reach the vulnerable code path via POST /api/auth/sign-up/email without authentication.
Check the vendor advisory for the affected versions of Lumiverse. Attack surface: POST /api/auth/sign-up/email.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.9.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/auth/sign-up/email requests with malformed payloads or SQL meta-characters. Run grep -r 'Lumiverse' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Lumiverse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Lumiverseを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/auth/sign-up/email' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/auth/sign-up/emailへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Lumiverse to 0.9.7ステージング環境で 0.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/auth/sign-up/email on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com