CVE-2025-10669
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 · uneditedA vulnerability was detected in Airsonic-Advanced up to 10.6.0. This vulnerability affects unknown code of the component Playlist Upload Handler. Performing manipulation results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used.
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 confidenceAirsonic-Advanced up to version 10.6.0 contains an unrestricted file upload vulnerability in the Playlist Upload Handler component. An authenticated or unauthenticated remote attacker can upload arbitrary files (including potentially malicious executables) to the server without proper validation of file types, extensions, or content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Airsonic-Advanced installationLocate the Airsonic-Advanced application on your system. Check for the 'airsonic.war' file, or look for the airsonic directory in your web application server (such as Tomcat's webapps folder). The application typically runs on port 8080 or 8080 with a /airsonic context path.Affected if Airsonic-Advanced is present on the server.
-
Verify the installed versionCheck the version of Airsonic-Advanced. This can typically be found in the war file name, in the application interface under 'About' or 'System' settings, or by examining the 'airsonic.war' file metadata. Compare your version to 10.6.0.Affected if The installed version is 10.6.0 or earlier (any version up to and including 10.6.0).
-
Confirm Playlist Upload Handler is accessibleAccess the playlist upload functionality. The endpoint is typically at /airsonic/upload.view or /airsonic/playlistUpload - check if this URL is reachable. Try accessing it with a web browser or curl command to see if the upload form or endpoint exists.Affected if The playlist upload endpoint is accessible without proper authentication restrictions or is exposed to unauthenticated users.
-
Inspect file upload configurationExamine the Airsonic-Advanced configuration files (airsonic.properties or similar) for any file upload validation settings. Look for properties related to upload restrictions, file type validation, or allowed extensions.Affected if No file type/extension restrictions are configured, or the configuration allows arbitrary file uploads for playlists.
You are affected if Airsonic-Advanced version 10.6.0 or earlier is installed AND the Playlist Upload Handler is accessible with insufficient validation controls.
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 file upload validation in the Playlist Upload Handler: restrict allowed file extensions to safe playlist formats (e.g., .m3u, .pls, .xspf), validate MIME types, sanitize filenames, and store uploads outside the webroot or in a non-executable directory.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10669 — 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-10669 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