Advplyr
Monthly
Unauthenticated arbitrary file read in audiobookshelf exploits a URL-encoding normalization gap between the Express authentication-exemption regex (which reads raw percent-encoded req.path) and Express's route parameter decoder (which decodes %2F sequences before handler execution), allowing any remote attacker to traverse the filesystem via crafted cover art requests. This directly bypasses the prior fix for CVE-2025-25205, which had anchored the auth-exemption regex to req.path - meaning the root cause was incompletely remediated. No CISA KEV listing or confirmed public exploit exists at time of analysis, but the AV:N/AC:L/PR:N/UI:N profile and bypass-of-prior-patch nature make this high priority for all internet-facing audiobookshelf deployments.
JWT token type confusion in Audiobookshelf prior to 2.36.0 allows any holder of a valid refresh token to authenticate API and WebSocket endpoints (such as /api/me) that should only accept bearer access tokens. The jwtAuthCheck function in server/auth/TokenManager.js failed to validate the token's type claim, meaning refresh tokens - which are supposed to be restricted solely to the /auth/refresh endpoint - were silently accepted as legitimate session credentials across the entire API surface. No public exploit or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 score of 5.3 with PR:L reflects that exploitation requires prior possession of a refresh token.
Path traversal in Audiobookshelf's podcast creation endpoint allows attackers to write files outside the intended library directory by supplying a crafted file path. Affected versions are all releases prior to 2.32.2 (per CVE) or 2.33.2 (per EUVD - see confidence notes), with the vulnerable code located in server/controllers/PodcastController.js. No public exploit code has been identified and CISA KEV has not flagged active exploitation, but SSVC marks the attack as automatable, meaning scripted mass-scanning is feasible once a reliable exploit exists.
Stored cross-site scripting (XSS) in Audiobookshelf prior to 2.33.0 allows authenticated administrators to inject malicious HTML and JavaScript into the authLoginCustomMessage field via the /api/auth-settings endpoint, which is then rendered on the login page for all users without sanitization. This enables attackers with admin credentials to capture user credentials, perform account takeover, or redirect users to phishing sites. No public exploit code identified at time of analysis.
Denial-of-service in Audiobookshelf prior to version 2.32.2 allows authenticated admin users to crash the server by uploading a specially crafted ZIP file to the backup upload endpoint. The vulnerability stems from decompressing ZIP entries without size limits, enabling an attacker to craft a highly compressed archive that consumes gigabytes of memory when extracted, exhausting server resources and triggering an out-of-memory condition.
Authenticated users with upload permission in Audiobookshelf prior to 2.32.2 can enumerate files outside their authorized library folder through a path traversal vulnerability in the POST /api/filesystem/pathexists endpoint. The vulnerability exploits a weak String.startsWith() validation that fails to distinguish between sibling directories with shared prefixes (e.g., /audiobooks and /audiobooks-private), allowing information disclosure about file existence across library boundaries despite authentication requirements. No public exploit code or active exploitation has been identified at time of analysis.
Audiobookshelf prior to version 2.32.2 fails to enforce library access controls on the GET /api/collections and GET /api/collections/:id endpoints, allowing authenticated users to enumerate and retrieve collection metadata and book information from libraries they are not authorized to access. An attacker with valid credentials to any library can exploit this privilege escalation to discover sensitive metadata across all libraries in a multi-library installation.
Authenticated users with download permissions in Audiobookshelf prior to 2.32.2 can download files from libraries they do not have access to by directly specifying item IDs in the GET /api/libraries/:id/download endpoint, bypassing library access controls. An attacker with valid credentials and access to any single library can exfiltrate complete file contents from restricted libraries, including those explicitly denied to them.
Unauthenticated arbitrary file read in audiobookshelf exploits a URL-encoding normalization gap between the Express authentication-exemption regex (which reads raw percent-encoded req.path) and Express's route parameter decoder (which decodes %2F sequences before handler execution), allowing any remote attacker to traverse the filesystem via crafted cover art requests. This directly bypasses the prior fix for CVE-2025-25205, which had anchored the auth-exemption regex to req.path - meaning the root cause was incompletely remediated. No CISA KEV listing or confirmed public exploit exists at time of analysis, but the AV:N/AC:L/PR:N/UI:N profile and bypass-of-prior-patch nature make this high priority for all internet-facing audiobookshelf deployments.
JWT token type confusion in Audiobookshelf prior to 2.36.0 allows any holder of a valid refresh token to authenticate API and WebSocket endpoints (such as /api/me) that should only accept bearer access tokens. The jwtAuthCheck function in server/auth/TokenManager.js failed to validate the token's type claim, meaning refresh tokens - which are supposed to be restricted solely to the /auth/refresh endpoint - were silently accepted as legitimate session credentials across the entire API surface. No public exploit or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 score of 5.3 with PR:L reflects that exploitation requires prior possession of a refresh token.
Path traversal in Audiobookshelf's podcast creation endpoint allows attackers to write files outside the intended library directory by supplying a crafted file path. Affected versions are all releases prior to 2.32.2 (per CVE) or 2.33.2 (per EUVD - see confidence notes), with the vulnerable code located in server/controllers/PodcastController.js. No public exploit code has been identified and CISA KEV has not flagged active exploitation, but SSVC marks the attack as automatable, meaning scripted mass-scanning is feasible once a reliable exploit exists.
Stored cross-site scripting (XSS) in Audiobookshelf prior to 2.33.0 allows authenticated administrators to inject malicious HTML and JavaScript into the authLoginCustomMessage field via the /api/auth-settings endpoint, which is then rendered on the login page for all users without sanitization. This enables attackers with admin credentials to capture user credentials, perform account takeover, or redirect users to phishing sites. No public exploit code identified at time of analysis.
Denial-of-service in Audiobookshelf prior to version 2.32.2 allows authenticated admin users to crash the server by uploading a specially crafted ZIP file to the backup upload endpoint. The vulnerability stems from decompressing ZIP entries without size limits, enabling an attacker to craft a highly compressed archive that consumes gigabytes of memory when extracted, exhausting server resources and triggering an out-of-memory condition.
Authenticated users with upload permission in Audiobookshelf prior to 2.32.2 can enumerate files outside their authorized library folder through a path traversal vulnerability in the POST /api/filesystem/pathexists endpoint. The vulnerability exploits a weak String.startsWith() validation that fails to distinguish between sibling directories with shared prefixes (e.g., /audiobooks and /audiobooks-private), allowing information disclosure about file existence across library boundaries despite authentication requirements. No public exploit code or active exploitation has been identified at time of analysis.
Audiobookshelf prior to version 2.32.2 fails to enforce library access controls on the GET /api/collections and GET /api/collections/:id endpoints, allowing authenticated users to enumerate and retrieve collection metadata and book information from libraries they are not authorized to access. An attacker with valid credentials to any library can exploit this privilege escalation to discover sensitive metadata across all libraries in a multi-library installation.
Authenticated users with download permissions in Audiobookshelf prior to 2.32.2 can download files from libraries they do not have access to by directly specifying item IDs in the GET /api/libraries/:id/download endpoint, bypassing library access controls. An attacker with valid credentials and access to any single library can exfiltrate complete file contents from restricted libraries, including those explicitly denied to them.