CVE-2026-124834: iomad Password Field company_user.php store_temporary_password information disclosure

Published Nov 9, 2026
·
Updated

A security vulnerability has been detected in iomad up to 4.5.15/5.0.11/5.1.8/5.2.4. Affected by this issue is the function storetemporarypassword of the file public/local/iomad/classes/companyuser.php of the component Password Field Handler. Such manipulation leads to information disclosure. The attack may be performed from remote. The attack requires a high level of complexity. The exploitation is known to be difficult. The name of the patch is 0d9c0ccaa8a77583f5dd92eb7be7fbbb8cc6ec9b/9c740fd254fd12d56d7be3b85ac5e9fb4f8c03d8/33755cdd551a84be423b1eaf784d405c1988dbad/7fcf9b52c539a67f3e46a8da6b42ab1d1f26295b. It is advisable to implement a patch to correct this issue. This CVE was requested by the vendor.

Affected Software

1 affected component
Iomad Iomad<=4.5.15, <=5.0.11, <=5.1.8, <=5.2.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade iomad to a version that resolves this vulnerability.

    Patch 0d9c0ccaa8a77583f5dd92eb7be7fbbb8cc6ec9b/9c740fd254fd12d56d7be3b85ac5e9fb4f8c03d8/33755cdd551a84be423b1eaf784d405c1988dbad/7fcf9b52c539a67f3e46a8da6b42ab1d1f26295b

Event History

Nov 9, 2026
CVE Published
via MITRE·07:15 PM
Data Sourced
via MITRE·07:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which iomad versions are affected?

iomad versions up to 4.5.15, 5.0.11, 5.1.8, and 5.2.4 are affected.

2

Can this be exploited remotely without authentication?

The attack may be performed remotely, and the supplied vector lists no privileges or user interaction requirements. Exploitation requires high complexity and is described as difficult.

3

What is the impact of successful exploitation?

Successful exploitation can disclose information through the Password Field Handler's store_temporary_password function. No integrity or availability impact is identified in the supplied severity vector.

4

What should teams do to remediate this issue?

Implement the vendor-provided patch. The listed patch identifiers are 0d9c0ccaa8a77583f5dd92eb7be7fbbb8cc6ec9b, 9c740fd254fd12d56d7be3b85ac5e9fb4f8c03d8, 33755cdd551a84be423b1eaf784d405c1988dbad, and 7fcf9b52c539a67f3e46a8da6b42ab1d1f26295b.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203