Improper authorization in dhikshitha29 Insurance-Management-System policy holder updates

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-114249?

CVE-2026-114249 is a vulnerability classified as Improper Authorization and Incorrect Privilege Assignment, affecting Insurance-Management-System (affected versions: 91de5edda5baa109ad8e9baf03ce6a3ceda84183 and 125362cc21dca20d74091a4913a5096bb58dd837). This vulnerability is rated Medium, with a CVSS score of 6.9. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

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 Policy_no 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 products and scope

dhikshitha29 Insurance-Management-System is affected in the Policy Holder Update Form component, specifically the /Agent/includes/UpdatePolicyHolder-inc.php backend.

  • The supplied record marks two commit-based repository revisions as affected.
  • The project uses rolling releases, so the CNA does not provide affected or updated version ranges.
  • No fixed release is confirmed. A newer rolling-release revision should not be assumed safe without vendor or CNA evidence.

Technical details

The affected component is the Policy Holder Update Form, specifically /Agent/includes/UpdatePolicyHolder-inc.php. The backend accepts Policy_no and other update fields from a POST request, selects a record by that value, and performs an update without verifying the caller's session or ownership of the record. The technical report states that the code has no session_start(), no check of $_SESSION['sessionId'], and no comparison between the policy's Agency_code and the caller's identity. Because the record key is supplied by the client, an attacker can select another policy holder, creating an IDOR-like condition combined with missing authorization. The endpoint is remotely reachable without authentication or user interaction. The exact internal processing beyond the documented endpoint remains incompletely described.

Exploitability

The flaw can be reached over the network by sending a request to the policy-holder update backend. The normalized record and technical report indicate that authentication and user interaction are not required and that exploitation has low complexity. The public issue describes successful modification without a session cookie, and VulDB records a public proof-of-concept. The available evidence confirms public exploit availability but does not name a campaign, victim, or specific in-the-wild exploitation activity. The project was notified through an issue, but no response or confirmed fix is documented.

Technical impact

The directly demonstrated technical outcome is unauthorized modification of policy-holder records through the update backend. This breaks the authorization boundary between agents, agencies, and policy records, and could affect many records if policy numbers can be guessed or obtained. The public report also describes possible storage of HTML or script content that could later be rendered in administrative views, creating an additional consequence that requires deployment-specific validation. The available evidence focuses on unauthorized writes and does not establish arbitrary code execution, full database disclosure, or confirmed service disruption.

Business impact

An attacker can modify policy-holder names, telephone numbers, email addresses, addresses, nominee information, and dates of birth. These unauthorized writes can corrupt business records, disrupt agent or administrator workflows, and reduce confidence in insurance data. The technical report states that replacement of personal data could support identity fraud or social engineering against affected individuals. It also describes a possible ability to place HTML or script content into fields later rendered without escaping in administrator and agent views; that secondary consequence should be validated in each deployment.

Remediation

  1. No vendor patch, fixed release, or confirmed mitigation is provided in the record. Do not treat an arbitrary rolling-release revision as fixed.
  2. If source changes are possible, add server-side authentication checks before processing the update request and require a valid agent session.
  3. Enforce object-level authorization by validating that the requested Policy_no belongs to the caller's authorized agency and identity. Do not rely on the presentation-layer form to enforce access control.
  4. Add regression tests for unauthenticated requests, cross-agency policy updates, and attempts to change the target record by modifying Policy_no.
  5. Until the code is corrected, consider removing the endpoint from Internet access or replacing the affected component or product. This is a risk-reduction measure, not a vendor-confirmed fix.
  6. Review policy_holder change history, validate record integrity, and restore unauthorized changes if suspicious activity is found.

Detection

  1. Inventory deployments of dhikshitha29 Insurance-Management-System and determine whether /Agent/includes/UpdatePolicyHolder-inc.php and the Policy Holder Update Form are exposed through the web application.
  2. Compare deployed source with the commit-based revisions marked affected in the record, without assuming that an arbitrary newer rolling-release revision is fixed.
  3. Review web access logs, where request headers are retained, for POST requests to this endpoint without a valid session or with a success response such as success=PolicyAdded. Treat this as an investigation lead, not as a confirmed IOC.
  4. Review database audit logs or change history for policy_holder updates that are not associated with an authenticated agent authorized for the corresponding policy.
  5. In a staging environment, verify that unauthenticated requests are rejected and that an agent cannot update a policy belonging to another agency. Lack of suspicious log evidence does not prove that exploitation did not occur.
Sources (12)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.