CVE-2026-114249: dhikshitha29 Insurance-Management-System Policy Holder Update Form UpdatePolicyHolder-inc.php improper authorization
A vulnerability was detected in dhikshitha29 Insurance-Management-System 91de5edda5baa109ad8e9baf03ce6a3ceda84183/125362cc21dca20d74091a4913a5096bb58dd837. This vulnerability affects unknown code of the file /Agent/includes/UpdatePolicyHolder-inc.php of the component Policy Holder Update Form. The manipulation of the argument Policyno results in improper authorization. It is possible to launch the attack remotely. The exploit is now public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Instances of dhikshitha29 Insurance-Management-System that expose the Policy Holder Update Form and its /Agent/includes/UpdatePolicyHolder-inc.php endpoint are potentially exposed. The attack can be launched remotely.
What does an attacker need to exploit it?
The reported manipulation point is the Policy_no argument. No privileges or user interaction are indicated in the provided severity vector, and the attack complexity is rated low.
What is the likely impact of successful exploitation?
Successful exploitation may affect the confidentiality, integrity, and availability of policy-holder-related data or functionality, each with a low assessed impact. The underlying flaw is improper authorization in the update workflow.
How should teams handle version identification and remediation?
The project uses rolling releases, so affected and fixed release version details are unavailable. Review deployments based on the identified code revisions or inspect the Policy Holder Update Form handling of Policy_no, and monitor the project for a response or remediation.
Is public exploitation information available?
Yes. The exploit is reported as public and may be used, which increases the urgency of reviewing exposed instances and restricting access to the affected update functionality where feasible.