CVE-2024-28853
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 · uneditedAmpache is a web based audio/video streaming application and file manager. Stored Cross Site Scripting (XSS) vulnerability in ampache before v6.3.1 allows a remote attacker to execute code via a crafted payload to serval parameters in the post request of /preferences.php?action=admin_update_preferences. This vulnerability is fixed in 6.3.1.
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 confidenceStored Cross Site Scripting (XSS) vulnerability in Ampache versions before v6.3.1 allows authenticated remote attackers to inject malicious JavaScript code via crafted POST parameters to the /preferences.php?action=admin_update_preferences endpoint. The malicious payload is stored and executed when other users view the affected preferences.
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< 6.3.1CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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 installed Ampache versionLocate the version file or check the admin interface for the Ampache version number. Common locations include a VERSION file in the root directory or the admin system information page.Affected if The installed version is earlier than 6.3.1 (e.g., 6.3.0, 6.2.x, etc.)
-
Verify admin authentication is requiredConfirm that the /preferences.php?action=admin_update_preferences endpoint requires an authenticated admin session by attempting to access it or reviewing access control configuration.Affected if The endpoint is accessible to authenticated administrators; an attacker would need valid admin credentials to exploit this flaw
-
Inspect stored preferences for XSS payloadsQuery the database or navigate to the preferences section in the admin interface to view stored preference values. Look for any unexpected HTML, JavaScript, or script tags within preference fields.Affected if Any preference values contain raw HTML tags, script elements, or JavaScript event handlers that could execute in a user browser
-
Review web server access logsExamine web server access logs for POST requests to /preferences.php with the action=admin_update_preferences parameter, especially those containing suspicious characters like <script>, javascript:, or event handlers.Affected if Logs show POST requests to this endpoint containing XSS-like patterns in the parameter values
A user is affected if their Ampache installation is version 6.3.0 or earlier AND they have admin accounts that could be leveraged to inject malicious scripts through the admin_update_preferences endpoint.
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 · scoped6.3.1
Upgrade to Ampache v6.3.1 or later to remediate this vulnerability. As this is an authenticated admin-area vulnerability, also review admin account access and consider implementing input validation and output encoding as defense-in-depth.
Ampache 6.3.1
- Back up the current Ampache installation and database before upgrading
- Download Ampache version 6.3.1 or later from the official Ampache repository or distribution channel
- Upgrade the Ampache installation to version 6.3.1 following standard upgrade procedures
- Verify the upgrade was successful by accessing the application and confirming the version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28853 — 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-2024-28853 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