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

Published Sep 16, 2026
·
Updated

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.

Affected Software

1 affected component
SIMAC MyPHR=1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Fix the missing server-side ownership validation by ensuring the authenticated user is authorized to modify the employee record identified by {id} before allowing PUT operations (prevents IDOR).

    SIMAC MyPHR Server-side ownership validation for /api/employes/put/{id} = enabled
  2. Compensating control

    Restrict access to the SIMAC MyPHR employee update endpoint (/api/employes/put/{id}) so that authenticated users can only reach resources they are authorized to own; enforce this at the server with proper authorization/ownership checks for the employee identifier in the path (mitigates IDOR leading to account takeover and sensitive record access).

Event History

Sep 16, 2026
CVE Published
via MITRE·05:39 PM
Data Sourced
via MITRE·05:39 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What level of access does an attacker need to exploit this issue?

The attacker must be authenticated with a valid account. No user interaction is required, and the vulnerable endpoint is reachable over the network.

2

What can an attacker do after exploiting the issue?

An authenticated attacker can modify arbitrary employee records, including setting a controlled password to take over another employee account. They can also enumerate employee records and access sensitive PII, including private pay bulletins.

3

What request behavior enables account takeover?

The issue is triggered by sending a PUT request to /api/employes/put/{id} with an arbitrary employee identifier and a controlled password value. The endpoint lacks server-side validation that the requester owns the targeted employee record.

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