CVE-2025-46544
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 · uneditedIn Sherpa Orchestrator 141851, a low-privileged user can elevate their privileges by creating new users and roles.
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 confidenceSherpa Orchestrator 141851 contains an authorization bypass allowing low-privileged users to create new users and roles, effectively escalating their own privileges to administrative levels. The vulnerability indicates missing or insufficient access control checks on user/role management functions.
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 data= 141851CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 installed Sherpa Orchestrator versionAccess the Sherpa Orchestrator admin console or run 'about'/'version' command in the CLI to retrieve the exact build version numberAffected if The version displayed is exactly 141851
-
Verify user management API accessibilityUsing a low-privileged test account, attempt to access user creation endpoints (e.g., POST /api/users or /api/roles) via REST API call or web interfaceAffected if The low-privileged account can successfully submit requests to create users or roles without receiving a 403 Forbidden or authorization error
-
Inspect access control configurationReview the Sherpa Orchestrator configuration files or RBAC settings, typically found in authz.conf, rbac.json, or the admin security settings panelAffected if No role-based restrictions exist for user/role management functions, or 'create user' permission is assigned to non-admin roles
-
Audit for unauthorized administrative accountsList all users and roles in the system via admin console or API query, then check for accounts with administrator privileges that were not created by known admin usersAffected if New administrative users or roles exist that were created by low-privileged accounts
-
Review authentication logs for privilege escalationExamine Sherpa Orchestrator audit or authentication logs for events where non-admin accounts successfully called user/role management endpointsAffected if Logs show successful user/role creation requests from accounts lacking administrative permissions
You are affected if running Sherpa Orchestrator version 141851 and low-privileged users can access or successfully create users and roles without proper authorization checks.
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 strict role-based access control (RBAC) enforcement ensuring only designated administrators can create users and roles, combined with comprehensive authorization validation on all user management API endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46544 — 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-46544 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