CVE-2026-47094: SIMAC MyPHR IDOR Auth Bypass Vulnerability

CVE-2026-47094 Overview

CVE-2026-47094 is an insecure direct object reference (IDOR) vulnerability in SIMAC MyPHR 1.1, a human resources management application. The flaw resides in the employee update API endpoint, which fails to enforce server-side ownership validation. Authenticated attackers can send a crafted PUT request to the employees endpoint using an arbitrary employee identifier and a controlled password value. This allows account takeover, enumeration of employee records, and retrieval of sensitive personally identifiable information (PII) including private pay bulletins. The weakness is classified under CWE-639: Authorization Bypass Through User-Controlled Key.

Critical Impact

Any authenticated user can overwrite the credentials of any other employee account, resulting in full horizontal and vertical account takeover across the MyPHR platform.

Affected Products

• SIMAC MyPHR 1.1
• SIMAC HR Management Software deployments exposing the /api/employes endpoint
• Downstream integrations relying on MyPHR employee identity data

Discovery Timeline

• 2026-09-16 - CVE-2026-47094 published to NVD
• 2026-09-16 - Last updated in NVD database

Technical Details for CVE-2026-47094

Vulnerability Analysis

SIMAC MyPHR 1.1 exposes a REST API for managing employee records. The employee update endpoint accepts an employee identifier supplied in the request path or body. The server processes the update using this attacker-controlled key without verifying that the authenticated session owns the target record.

The endpoint accepts a password field within the update payload. When the server persists the update, it overwrites the target account's credentials with the attacker-supplied value. The attacker then authenticates as the victim using the new password. Because employee identifiers are sequential integers, attackers can iterate through the identifier space to enumerate and hijack every account.

Retrieved data includes personally identifiable information, employment metadata, and private pay bulletins. Compromise of privileged accounts extends the impact to administrative HR functions.

Root Cause

The root cause is missing server-side authorization on the employee update handler. The application trusts the client-supplied employee identifier as the target of the operation. It does not compare the identifier against the authenticated session's employee context. This is a textbook CWE-639 authorization bypass through a user-controlled key.

Attack Vector

The attack requires only low-privileged authenticated access to MyPHR. An attacker logs in with any valid employee account, then issues a PUT request to the employee update endpoint targeting a different employee identifier. The request body includes a new password value. After the server accepts the update, the attacker authenticates as the victim. Full technical details and a proof of concept are available in the VulnCheck advisory and the public GitHub Gist PoC.

No verified code examples are published beyond the referenced advisory. Refer to the vendor advisory for exploitation specifics.

Detection Methods for CVE-2026-47094

Indicators of Compromise

• PUT requests to /api/employes/{id} where the {id} value does not match the authenticated user's employee identifier
• Unexpected password change events on employee records without a corresponding password reset workflow
• Bulk sequential access patterns against /api/employes/{id} endpoints from a single session or source IP
• Login events from unusual geolocations or user agents immediately following an out-of-band password update

Detection Strategies

• Correlate application access logs with authenticated session identity to flag any update where the request path identifier differs from the session's employee identifier
• Alert on password field mutations occurring through the employee update endpoint rather than the dedicated password reset flow
• Baseline normal PUT request rates per user and alert on enumeration-style bursts targeting sequential identifiers

Monitoring Recommendations

• Forward MyPHR web server and application logs to a centralized SIEM for correlation with authentication events
• Enable audit logging on all employee record modifications, capturing actor identity, target identity, and modified fields
• Monitor for anomalous account takeover indicators such as sudden changes in login source followed by data export activity

How to Mitigate CVE-2026-47094

Immediate Actions Required

• Restrict network exposure of the MyPHR API to trusted internal networks or VPN users until a patch is applied
• Force password resets for all employee accounts and invalidate active sessions to evict any pre-existing attacker footholds
• Review audit logs for PUT /api/employes/{id} activity where the target identifier does not match the session identity
• Contact SIMAC support to confirm patch availability for MyPHR 1.1

Patch Information

No vendor patch reference is published in the enriched CVE data at the time of writing. Refer to the SIMAC HR Management Software product page and the VulnCheck advisory for the current remediation status. The fix must enforce server-side authorization by validating that the authenticated session owns the target employee record before processing updates.

Workarounds

• Deploy a web application firewall (WAF) rule that blocks PUT requests to /api/employes/{id} where the path identifier does not match the JWT or session-bound employee identifier
• Introduce a reverse proxy filter that rejects employee update payloads containing a password field, forcing credential changes through the intended reset workflow
• Segment MyPHR from broader corporate networks and require multi-factor authentication at the identity provider layer to limit the value of stolen credentials