Summary
The AudioIgniter WordPress plugin exposes a playlist endpoint that accepts a user-controlled playlist ID and returns full track metadata without verifying authentication, capabilities, or post status.
As a result, unauthenticated attackers can enumerate and view metadata (titles, artists, audio URLs, buy links, download URLs, and cover images) for any playlist on the site, including those marked draft, private, pending, or in trash.
Affected context
This vulnerability occurs in WordPress sites using the AudioIgniter plugin where the handle_playlist_endpoint() function is reachable via the audioigniter_playlist_id query parameter or the /audioigniter/playlist/{id}/ rewrite rule.
The issue manifests when playlists of any status (e.g., draft, private, pending, trash) are stored as posts, and the endpoint returns track metadata while only validating post_type and not enforcing authentication, authorization, or publication checks.
Sites that host sensitive or proprietary audio content, pre-release playlists, or restricted media via AudioIgniter are particularly affected.
Exploit preconditions
- Attack surface: Public-facing WordPress endpoints provided by the AudioIgniter plugin.
- Required access: No authentication required; any external user or bot can send HTTP requests.
- Trigger point: Issuing a request with a chosen playlist identifier via:
?audioigniter_playlist_id={id}query variable, or- the
/audioigniter/playlist/{id}/pretty permalink route. - Why exploitation is possible: The
handle_playlist_endpoint()function: - Accepts a user-controlled post/playlist ID.
- Only verifies that the post is of the expected
post_type. - Does not check user capabilities, authentication status, or
post_status(e.g., private, draft). - Responds with full track metadata for the referenced playlist.
Why this happens
The root cause is an Insecure Direct Object Reference (IDOR) pattern where internal object identifiers (playlist post IDs) are exposed and trusted without adequate access control.
The endpoint directly maps user-supplied IDs to playlist posts and returns associated metadata after verifying only the post_type.
This maps to CWE-639: Authorization Bypass Through User-Controlled Key, where an application relies solely on user-provided IDs to access resources without confirming the requesting user's authorization or the resource's visibility (such as post_status).
Conceptually, the bug arises from treating numeric IDs as safe selectors instead of guarded references and failing to enforce both authentication and object-level authorization on read operations.
Potential impact
- Unauthenticated users may access track metadata for private or draft playlists.
- Pre-release, internal, or members-only audio content metadata could be exposed prematurely.
- Audio URLs and download links can be harvested and shared without permission.
- Commercial or licensed media references (buy links, download URLs) may be scraped at scale for competitive or abusive purposes.
- Internal naming conventions, collaboration details, or artwork (cover images) associated with non-public playlists may be revealed.
General mitigation guidance
Mitigation typically focuses on enforcing robust access control at the resource level and avoiding trust in user-supplied identifiers.
Common defensive patterns include:
- Apply authentication checks to all endpoints that return playlist or media metadata, ensuring only intended users can access non-public content.
- Enforce object-level authorization: verify user capabilities and ownership before returning data based on a playlist ID, especially for
post_statusvalues likeprivate,draft,pending, ortrash. - Filter by visibility status so that endpoints serving unauthenticated users only return content that is explicitly public or published.
- Avoid direct use of raw post IDs in public APIs; consider scoped or opaque identifiers where suitable, combined with server-side authorization checks.
- Design secure-by-default endpoints where the absence of explicit permission results in no data being returned, and all new routes are required to declare their access control behavior.
How teams detect issues like this
Organizations can detect this type of IDOR issue through a combination of review and testing:
- Code review signals:
- Functions that accept IDs directly from query parameters or URL paths (e.g.,
$_GET,WP_Query, or rewrite rules) and immediately load posts or playlists. - Endpoints that only check
post_typeor existence but omit checks for capabilities,post_status, or user identity. - Public handlers hooked into events like
template_redirectthat return JSON or structured metadata. - Static analysis patterns:
- Rules that flag routes or handlers using user-controlled IDs to retrieve database records without subsequent capability/authorization checks.
- Detection of access to post data fields (titles, meta, URLs) that is not gated by
current_user_can()or equivalent checks. - Dynamic and integration testing:
- Automated tests or API fuzzers that iterate over playlist IDs (sequential or guessed) and verify whether non-public items are returned to an unauthenticated client.
- Security pipeline integration:
- Incorporating automated security review tools in CI that highlight newly added unauthenticated endpoints accessing posts, media, or other resources based solely on client-supplied IDs.

