Quick answers
- Is CVE-2026-114249 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114249 being exploited in the wild.
- How severe is CVE-2026-114249?
- High severity, with a CVSS score of 7.3, published 21 October 2026.
- Which products and versions are affected?
- Dhikshitha29 Insurance-Management-System commit 125362cc21dca20d74091a4913a5096bb58dd837 and earlier.
- Is there a fix for CVE-2026-114249?
- 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-114249 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-114249?
- Check whether you run Dhikshitha29 Insurance-Management-System at an affected version. 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
The UpdatePolicyHolder-inc.php endpoint processes policy holder updates via POST but performs no session validation or ownership check, making it vulnerable to insecure direct object reference (IDOR). An attacker can craft a POST request with any Policy_no and field values to overwrite personal data of any policyholder. The fix requires adding session verification and validating that the policy belongs to the authenticated user's agency.
Affected products
- dhikshitha29 Insurance-Management-System commit 125362cc21dca20d74091a4913a5096bb58dd837 and earlier
Timeline
- 2026-10-07: disclosed
- 2026-10-21: advisory