CVE-2025-49652
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authentication in the registration feature of Lablup's BackendAI allows arbitrary users to create user accounts that can access private data even when registration is disabled.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe registration endpoint in BackendAI lacks proper authentication checks, allowing any unauthenticated user to create accounts via direct API calls. This bypasses administrator-configured registration settings, enabling attackers to obtain valid user credentials and access private data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify BackendAI installationCheck if BackendAI is running in the environment by looking for backendai-related processes, containers, or services. Search for 'backendai' in running processes or container listings.Affected if BackendAI is present and running in the environment
-
Locate the registration API endpointIdentify the registration endpoint path by reviewing BackendAI API documentation or by checking the application's API routing configuration. Common paths include /api/v1/register, /auth/register, or similar registration-related routes.Affected if A registration endpoint exists and accepts POST requests for account creation
-
Test unauthenticated account creationSend a POST request to the registration endpoint with a test payload (username, password, email) WITHOUT including any authentication headers or tokens. Observe the HTTP response code.Affected if The request succeeds with a 200 or 201 status and returns a valid authentication token or user creation confirmation without requiring credentials
-
Verify admin registration settings are bypassedCheck BackendAI's configuration files or admin panel for registration restrictions (such as 'allow_registration', 'require_admin_approval', or 'self_registration_enabled' settings). Then confirm whether these settings are being ignored by the vulnerable endpoint.Affected if Admin-configured registration restrictions exist but the endpoint still allows unauthenticated account creation
If the registration endpoint accepts unauthenticated POST requests and creates valid user accounts despite admin-configured restrictions, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authentication enforcement on the registration endpoint, ensuring that account creation requires valid admin credentials or approval even when self-registration is disabled.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49652 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data