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.
CVE-2026-47094
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 56(Track*)EG Risk 56/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 17, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026SIMAC MyPHR 1.1 IDOR Account Takeover via /api/employes/put/{id} | Advisories | VulnCheck
https://www.vulncheck.com/advisories/simac-myphr-idor-account-takeover-via-api-employes-put-idLogiciel de gestion des ressources humaines - SIMAC | ESN Société informatique | éditeur logiciel ERP
https://it.simac.tn/nos-solutions/logiciel-de-gestion-des-ressources-humaines/CVE-2026-47094 · GitHub
https://gist.github.com/LnPaulin/33e9b08ef0e26198afbfcc1343850682Vendor Advisories for CVE-2026-47094(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 20:14 UTCGHSA enrichment
- 2026-09-20 07:52 UTCGHSA enrichment
- 2026-09-19 19:28 UTCEG score recompute
- 2026-09-19 19:28 UTCGHSA enrichment
- 2026-09-19 07:07 UTCEG score recompute
- 2026-09-19 07:07 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:45 UTCGHSA enrichment
- 2026-09-18 06:24 UTCEG score recompute
- 2026-09-18 06:24 UTCGHSA enrichment
- 2026-09-17 18:00 UTCEG score recompute
- 2026-09-17 18:00 UTCGHSA enrichment
- 2026-09-17 06:45 UTCEG score recompute
- 2026-09-17 06:45 UTCGHSA enrichment
- 2026-09-16 18:24 UTCEG score recompute
- 2026-09-16 17:45 UTCEG score recompute
- 2026-09-16 17:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-47094?
When was CVE-2026-47094 disclosed?
Is CVE-2026-47094 actively exploited?
What is the CVSS score of CVE-2026-47094?
How do I remediate CVE-2026-47094?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47094
Is Your Infrastructure Affected by CVE-2026-47094?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.