CVE-2025-46545: XSS
First published: Fri Apr 25 2025(Updated: )
In Sherpa Orchestrator 141851, the functionality for adding or updating licenses allows for stored XSS attacks by an administrator through the name parameter. The XSS payload can execute when the license expires.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Sherpa Orchestrator |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-46545?
CVE-2025-46545 is classified as a high-severity vulnerability due to the potential for stored XSS attacks.
How do I fix CVE-2025-46545?
To fix CVE-2025-46545, ensure that input validation and sanitization are implemented for the name parameter when adding or updating licenses.
Who is affected by CVE-2025-46545?
CVE-2025-46545 affects users of Sherpa Orchestrator version 141851.
What type of attack is possible with CVE-2025-46545?
CVE-2025-46545 allows for stored cross-site scripting (XSS) attacks through the name parameter exploited by an administrator.
When can the XSS payload execute in relation to CVE-2025-46545?
The XSS payload in CVE-2025-46545 can execute when the added license expires.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/severity
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/sherpa
- canonical/sherpa orchestrator