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


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-gmr3-2h38-h26q

## What is CVE-2026-124834?

CVE-2026-124834 is a medium-severity vulnerability in iomad, published on 9 Nov 2026. 

### Official description

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 store_temporary_password of the file public/local/iomad/classes/company_user.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.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-124834?


## How do I fix CVE-2026-124834?

No fix has been published for CVE-2026-124834 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124834 being exploited?

There is no known exploitation of CVE-2026-124834 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124834 and fix it if it is affected.

What it is: CVE-2026-124834 is a medium-severity vulnerability in iomad, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124834 in the wild and no public exploit code.

Affected product: iomad. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124834/ (Markdown: https://insights.sbomify.com/CVE-2026-124834/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124834
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124834
- OSV: https://osv.dev/vulnerability/CVE-2026-124834

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124834/
Summaries are generated and may contain mistakes; the official description above is the record.