CVE-2026-47755: ITFlow authorization bypass in credential edit modal

CVE-2026-47755 · Severity: medium · CVSS 6.5 · Published 2026-07-23

ITFlow, an IT management and ticketing platform for service providers, contains a security flaw that allows staff members to view sensitive information they are not authorized to see. A technician with low-level access can bypass internal restrictions to view plaintext passwords and two-factor authentication (TOTP) secrets belonging to other clients. This could lead to unauthorized access to client systems and a significant breach of customer data privacy.

Technologies: ITFlow. Vendors: ITFlow.

Quick answers

Is CVE-2026-47755 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47755 being exploited in the wild.
How severe is CVE-2026-47755?
Medium severity, with a CVSS score of 6.5, published 23 July 2026.
Which products and versions are affected?
ITFlow < 26.05.
Is there a fix for CVE-2026-47755?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47755 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47755?
Check whether you run ITFlow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An Insecure Direct Object Reference (IDOR) vulnerability exists in ITFlow prior to version 26.05. The 'credential_edit.php' endpoint fails to implement client scoping or call 'enforceClientAccess()', allowing any authenticated agent to request an arbitrary 'credential_id'. By directly accessing the modal via a crafted GET request, an attacker can trigger the server to load and decrypt sensitive fields, including 'credential_password' and 'otp_secret', for records belonging to tenants they are not permitted to manage. A related AJAX endpoint 'get_totp_token_via_id' is also affected, allowing the generation of live 2FA codes for unauthorized records. The issue is resolved in version 26.05.

Affected products

  • itflow-org ITFlow < 26.05

Timeline

  • 2026-05-20: advisory: GitHub Security Advisory published
  • 2026-07-23: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.