CVE-2026-22238
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 · uneditedThe vulnerability exists in BLUVOYIX due to improper authentication in the BLUVOYIX admin APIs. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable admin API to create a new user with admin privileges. Successful exploitation of this vulnerability could allow the attacker to gain full access to customers' data and completely compromise the targeted platform by logging in to the newly-created admin user.
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 · moderate confidenceBLUVOYIX contains an authentication bypass vulnerability in its admin APIs where improper authentication allows unauthenticated attackers to send specially crafted HTTP requests that create new admin-level users. This grants the attacker complete platform access and customer data compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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.
-
Confirm Bluvoyix installation existsSearch for Bluvoyix components, services, or web applications in your environment. Check for directories named 'bluvoyix' or 'bluspark' and look for running services on common admin ports.Affected if Bluvoyix or Bluspark software is present in the environment
-
Identify admin API endpointsReview application routing configuration, OpenAPI/Swagger documentation, or network traffic to locate admin API paths. Common patterns include /admin/, /api/admin/, or /administrator/ endpoints.Affected if Admin API endpoints are accessible without authentication requirements visibly documented or enforced
-
Test admin API authentication enforcementSend a crafted HTTP POST request to identified admin endpoints (especially user creation paths) without including any authentication headers or tokens. Observe if the request is accepted or rejected.Affected if Requests to admin user creation APIs succeed without providing valid authentication credentials
-
Audit existing admin user accountsQuery the user database or admin panel to list all accounts with administrator privileges. Compare against known legitimate admin users and look for unexpected or recently created admin-level accounts.Affected if There are admin accounts that were not created by known legitimate administrators, especially accounts created recently or with suspicious usernames
-
Review API access logs for exploitation indicatorsExamine HTTP server logs, API gateway logs, or application logs for POST requests to user creation endpoints originating from unauthenticated IP addresses or containing abnormal patterns.Affected if Logs show unauthenticated requests to admin user creation endpoints or successful user creation events from unexpected sources
If Bluvoyix is deployed and admin APIs accept user creation requests without valid authentication or if unauthorized admin accounts exist, the environment is affected by this vulnerability.
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 proper authentication and authorization checks on all admin API endpoints, enforce authentication requirements, and invalidate any potentially compromised admin accounts. Consider implementing rate limiting and additional security controls on administrative functions.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22238 — 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-2026-22238 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