EUVD-2026-48334Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network-reachable endpoint (AV:N), trivial enumeration (AC:L), any agent account suffices (PR:L), only credential data exposed with no integrity or availability impact (C:H/I:N/A:N).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ITFlow provides an IT documentation, ticketing and accounting system for small managed service providers. Prior to version 26.05, low-privileged authenticated agent can retrieve plaintext credentials and TOTP secrets belonging to another client by directly requesting the credential edit modal with an arbitrary credential_id. The endpoint does not enforce client scoping or object-level authorization before loading and decrypting the credential record. Version 26.05 fixes the issue.
AnalysisAI
Insecure Direct Object Reference (IDOR) in ITFlow allows a low-privileged authenticated agent to exfiltrate plaintext credentials and TOTP secrets belonging to any client by supplying an arbitrary credential_id to the credential edit modal endpoint. The affected endpoint performs no client-scoping or object-level authorization check before loading and decrypting the stored credential record, making cross-client data access trivially achievable with any valid agent account. No active exploitation is confirmed (not in CISA KEV), but the high confidentiality impact (CVSS C:H) reflects the severity of exposing decrypted secrets and multi-factor authentication seeds across MSP client boundaries.
Technical ContextAI
ITFlow is a self-hosted, open-source IT management platform designed for small managed service providers, covering documentation, ticketing, and accounting. The vulnerable component is the credential edit modal endpoint, which accepts a user-controlled credential_id parameter to load and decrypt stored credential records. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), a class of IDOR where object access control is enforced only by the client-supplied key rather than by server-side scoping to the authenticated user's authorized data. Since ITFlow is multi-tenant by design - serving multiple clients under the same MSP instance - the absence of client-scope enforcement on this endpoint allows an agent authenticated to one client context to read decrypted credentials (including TOTP secrets) belonging to any other client. The CPE cpe:2.3:a:itflow-org:itflow:*:*:*:*:*:*:*:* confirms all versions prior to 26.05 are in scope.
RemediationAI
Vendor-released patch: ITFlow version 26.05. Upgrade immediately to v26.05, which enforces object-level authorization on the credential edit modal endpoint; the patch is confirmed by the GitHub advisory GHSA-987x-g5f9-2rpq and the code diff at https://github.com/itflow-org/itflow/compare/v26.04...v26.05. If immediate upgrade is not possible, restrict agent account creation to only fully trusted personnel and audit all existing agent accounts for necessity; this reduces the pool of potential abusers but does not eliminate the vulnerability. Additionally, review ITFlow access logs for anomalous credential_id enumeration patterns (sequential or out-of-scope IDs requested by a single agent session) as a detective control. Note that restricting network access to the ITFlow instance (e.g., VPN-only access) raises the bar for exploitation by reducing attacker access to agent credentials but does not remediate the underlying authorization flaw.
Cross Site Scripting vulnerability in ITFlow.org before commit v.432488eca3998c5be6b6b9e8f8ba01f54bc12378 allows a remto
An SQL injection vulnerability in Itflow through 25.06 has been identified in the "role_id" parameter when editing a pro
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today