SkywalkingApplication · Apache
CVE-2025-54057
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 · uneditedImproper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Apache SkyWalking. This issue affects Apache SkyWalking: <= 10.2.0. Users are recommended to upgrade to version 10.3.0, which fixes the 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 · high confidenceA basic Cross-Site Scripting (XSS) vulnerability (CWE-79) in Apache SkyWalking allows attackers to inject malicious HTML/script tags due to improper input neutralization. The vulnerability exists in the web interface of the observability platform.
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
SkywalkingApplication
< 10.3.0CVSS 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 Apache SkyWalking installationCheck for SkyWalking processes running (ps aux | grep skywalking) or look for installation directories like /opt/skywalking, /usr/local/skywalking, or the $SW_HOME environment variableAffected if Apache SkyWalking is found running or installed on the system
-
Determine installed SkyWalking versionCheck the version file in the installation directory (commonly found in config/VERSION or the startup script output), or query the web UI health endpointAffected if The installed version is lower than 10.3.0 (for example: 10.2.0, 10.1.0, 9.x, 8.x series)
-
Confirm web interface is accessibleCheck if the SkyWalking oap-server webapp is deployed and the port is listening (default 8080, check server.yml for web configuration). Use 'netstat -tlnp | grep -E "8080|8180"' or similar to identify open web portsAffected if The SkyWalking web interface port is exposed and accessible (the XSS only affects the web UI)
You are affected if Apache SkyWalking is installed with a version lower than 10.3.0 and the web interface is accessible.
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.
dbcve · scoped10.3.0
Upgrade Apache SkyWalking to version 10.3.0 which contains the fix for this XSS vulnerability.
10.3.0
- Download Apache SkyWalking version 10.3.0 from the official Apache SkyWalking release page
- Stop the currently running SkyWalking instance
- Backup your existing configuration and data directories
- Install version 10.3.0 following your deployment method (binary distribution, Docker, or source compilation)
- Restore your backed-up configuration files
- Start the upgraded SkyWalking instance
- Verify the web UI is accessible and the version displays as 10.3.0
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Skywalking
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54057 — 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-54057 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