CVE-2025-46547
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, the web application lacks protection against CSRF attacks, with resultant effects of an attacker conducting XSS attacks, adding a new user or role, or exploiting a SQL injection issue.
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 confidenceThe Sherpa Orchestrator 141851 web application lacks CSRF protection, allowing attackers to craft malicious requests that execute actions on behalf of authenticated users. This vulnerability can be leveraged to perform XSS attacks, add unauthorized users or roles, or trigger SQL injection vulnerabilities.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify Sherpa Orchestrator versionLocate and inspect the installed Sherpa Orchestrator version number through the application admin interface, system diagnostics, or installed packages/configuration files. Compare against version 141851.Affected if Installed version equals exactly 141851
-
Inspect forms for CSRF token presenceReview HTML source code of state-changing forms (user management, role assignment, configuration changes) to determine if a CSRF token or anti-CSRF token field is present in the form markup.Affected if Forms lack CSRF token fields or tokens are missing from form submissions
-
Verify SameSite cookie attributesExamine browser developer tools or proxy logs to inspect session cookies Set-Cookie headers for the SameSite attribute. Check if SameSite=Strict or SameSite=Lax is configured.Affected if Cookies lack SameSite attribute or have SameSite=None without Secure flag
-
Test state-changing endpoints for CSRF protectionSend a crafted request to state-changing API endpoints (user creation, role modification, data manipulation) without an anti-CSRF token to observe if the action executes successfully.Affected if Requests execute without CSRF token validation
Environment is affected if the installed Sherpa Orchestrator version is exactly 141851 and state-changing operations lack CSRF token validation or proper SameSite cookie attributes.
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 CSRF token validation for all state-changing operations and enforce SameSite cookie attributes to prevent cross-site request forgery, while also addressing the secondary XSS and SQL injection vectors.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46547 — 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-46547 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