Quick answers
- Is CVE-2026-14212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14212 being exploited in the wild.
- How severe is CVE-2026-14212?
- Medium severity, with a CVSS score of 4.7, published 26 August 2026.
- Which products and versions are affected?
- AmeliaBooFing Amelia Pro before 9.8.
- Is there a fix for CVE-2026-14212?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14212 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14212?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an insecure direct object reference (IDOR) vulnerability in the provider account update endpoint (/users/providers/PROVIDER_ID). An authenticated employee (provider) can send a password change request using a stolen or known provider ID without the application verifying ownership of that account. The vulnerability is triggered when the email field is omitted from the request; including an email field triggers an "Email already exist" validation that blocks the attack. An authenticated attacker can fully compromise another provider's Employee Panel account and access their schedule, bookings, and customers' personal data.
Affected products
- AmeliaBooFing Amelia Pro before 9.8
Timeline
- 2026-08-24: disclosed
- 2026-08-26: advisory