# CVE-2026-47094: SIMAC MyPHR 1.1 IDOR Account Takeover via /api/employes/put/{id}

> Authenticated attackers can take over accounts and access sensitive employee data by exploiting missing ownership validation in the employee update API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-7x6f-hv5j-6c4j

## What is CVE-2026-47094?

CVE-2026-47094 is a high-severity missing authorization vulnerability in SIMAC MyPHR, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SIMAC MyPHR 1.1 contains an insecure direct object reference (IDOR) vulnerability that allows authenticated attackers to access and modify arbitrary employee records due to missing server-side ownership validation. Attackers can send a PUT request to the employee update endpoint with an arbitrary employee identifier and a controlled password value to take over target accounts, enumerate employee records, and retrieve sensitive personally identifiable information including private pay bulletins.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-47094 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47094 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47094 is a high-severity missing authorization vulnerability in SIMAC MyPHR, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47094 exists.

Affected product: SIMAC MyPHR. 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-47094/ (Markdown: https://insights.sbomify.com/CVE-2026-47094/index.md)
```

## Sources

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

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