CVE-2025-60427
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 · uneditedLibreTime 3.0.0-alpha.10 and possibly earlier is vulnerable to Broken Access Control, where a user with the DJ role can access analytics data via the Web UI and direct API calls. The backend does not verify role-based permissions for analytics endpoints, allowing unauthorized retrieval of station-wide metrics. This results in information disclosure to less privileged users.
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 confidenceLibreTime 3.0.0-alpha.10 contains a Broken Access Control vulnerability where the backend fails to enforce role-based permissions on analytics endpoints. Users assigned the DJ role, which should only have broadcast permissions, can retrieve station-wide analytics data through the Web UI or direct API calls, resulting in unauthorized information disclosure.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify installed LibreTime versionCheck the version file or admin interface for the exact LibreTime version numberAffected if Version is 3.0.0-alpha.10 or falls within the alpha.10 release cycle without subsequent access control patches
-
Verify DJ role permissions configurationAccess the user role management section in the admin panel and confirm DJ role is assigned only broadcast permissionsAffected if DJ role exists and is intended to be restricted to broadcast-only access
-
Test analytics endpoint access with DJ accountLog in with a user assigned the DJ role and attempt to access analytics/dashboard endpoints via the Web UI or API (e.g., GET /api/analytics or /station/analytics)Affected if A DJ-role user can retrieve station-wide analytics data that should only be visible to admin or manager roles
-
Review API response authorization headersMake an authenticated API call as a DJ user to analytics endpoints and inspect whether the server returns data without returning a 403 Forbidden or unauthorized errorAffected if The server returns analytics data (200 OK) instead of rejecting the request based on role permissions
-
Check authentication vs authorization enforcementExamine server logs or use a proxy to observe whether analytics requests from DJ accounts are validated for both authentication (logged in) and authorization (correct role)Affected if Requests are authenticated (user is logged in) but not authorized (role check is missing or bypassed) before returning analytics data
A user is affected if running LibreTime 3.0.0-alpha.10 where DJ-role accounts can access station-wide analytics through the Web UI or API without proper authorization checks.
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 server-side authorization checks on all analytics endpoints to verify user role permissions before returning data. Restrict station-wide metrics to admin or manager roles only.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60427 — 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-60427 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