iomad up to 4.5.15/5.0.11/5.1.8/5.2.4 Password Field company_user.php store_temporary_password information disclosure

Summaryinfo

A vulnerability has been found in iomad up to 4.5.15/5.0.11/5.1.8/5.2.4 and classified as problematic. This affects the function store_temporary_password of the file public/local/iomad/classes/company_user.php of the component Password Field Handler. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2026-124834. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue. This CVE was requested by the vendor.

Detailsinfo

A vulnerability was found in iomad up to 4.5.15/5.0.11/5.1.8/5.2.4. It has been classified as problematic. This affects the function store_temporary_password of the file public/local/iomad/classes/company_user.php of the component Password Field Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.

The weakness was shared 10/02/2026 by Christian Schneider as 2831. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-124834. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

This CVE was requested by the vendor. By approaching the search of inurl:public/local/iomad/classes/company_user.php it is possible to find vulnerable targets with Google Hacking.

Applying the patch 0d9c0ccaa8a77583f5dd92eb7be7fbbb8cc6ec9b/9c740fd254fd12d56d7be3b85ac5e9fb4f8c03d8/33755cdd551a84be423b1eaf784d405c1988dbad/7fcf9b52c539a67f3e46a8da6b42ab1d1f26295b is able to eliminate this problem. The bugfix is ready for download at github.com. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• iomad

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.5.13
• 4.5.14
• 4.5.15
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4
• 5.0.5
• 5.0.6
• 5.0.7
• 5.0.8
• 5.0.9
• 5.0.10
• 5.0.11
• 5.1.0
• 5.1.1
• 5.1.2
• 5.1.3
• 5.1.4
• 5.1.5
• 5.1.6
• 5.1.7
• 5.1.8
• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4

License

• open-source

Website

• Product: https://github.com/iomad/iomad/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion