cssigniterteam AudioIgniter Music Player Plugin up to 2.0.2 on WordPress /audioigniter/playlist/ handle_playlist_endpoint authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in cssigniterteam AudioIgniter Music Player Plugin up to 2.0.2 on WordPress. This issue affects the function handle_playlist_endpoint of the file /audioigniter/playlist/. The manipulation leads to authorization.
This vulnerability is documented as CVE-2026-8679. The attack can be initiated remotely. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability was found in cssigniterteam AudioIgniter Music Player Plugin up to 2.0.2 on WordPress and classified as problematic. This issue affects the function handle_playlist_endpoint of the file /audioigniter/playlist/. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality. The summary by CVE is:
The AudioIgniter plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.0.2. This is due to the handle_playlist_endpoint() function (hooked to template_redirect) accepting a user-controlled playlist ID via the audioigniter_playlist_id query var or the /audioigniter/playlist/{id}/ rewrite rule and returning playlist track data without performing any authentication, capability, or post_status check — only the post_type is validated. This makes it possible for unauthenticated attackers to view track metadata (titles, artists, audio URLs, buy links, download URLs, and cover images) of any playlist on the site, including those in draft, private, pending, or trash status.
The weakness was released by Nudien Udin and Alfito Ardi Pratama. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-8679 since 05/15/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.0.2 eliminates this vulnerability. Applying the patch 35a0508583c26c01b6ac446404ad6fe1d440d8d4 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: AudioIgniter Music Player Plugin 2.0.2
Patch: 35a0508583c26c01b6ac446404ad6fe1d440d8d4
Timeline
05/15/2026 CVE reserved05/22/2026 Advisory disclosed
05/22/2026 VulDB entry created
05/22/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Nudien Udin, Alfito Ardi Pratama
Status: Confirmed
CVE: CVE-2026-8679 (🔒)
GCVE (CVE): GCVE-0-2026-8679
GCVE (VulDB): GCVE-100-365171
Entry
Created: 05/22/2026 11:46Changes: 05/22/2026 11:46 (69)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.