### Summary The ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. ### Technical Details The ticket creation endpoint accepted a user-supplied service identifier without verifying ownership or authorization against the authenticated account. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service. The vulnerability required authentication and did not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. ### Impact Successful exploitation could allow an authenticated user to: - Create support tickets referencing services belonging to other users - Potentially cause support staff to interact with or review unrelated customer services The vulnerability did not allow: - Direct access to another user's service - Modification of another user's service - Retrieval of confidential service data through the vulnerable endpoint itself
### Summary The ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. ### Technical Details The ticket creation endpoint accepted a user-supplied service identifier without verifying ownership or authorization against the authenticated account. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service. The vulnerability required authentication and did not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. ### Impact Successful exploitation could allow an authenticated user to: - Create support tickets referencing services belonging to other users - Potentially cause support staff to interact with or review unrelated customer services The vulnerability did not allow: - Direct access to another user's service - Modification of another user's service - Retrieval of confidential service data through the vulnerable endpoint itself
Update paymenter/paymenter to 1.5.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPaymenter has broken object level authorization via service reference manipulation on ticket creation affects paymenter/paymenter (composer). Severity is medium. ### Summary The ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. ### Technical Details The ticket creation endpoint accepted a user-supplied service identifier without verifying ownership or authorization against the authenticated account. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service. The vulnerability required authentication and did not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. ### Impact Successful exploitation could allow an authenticated user to: - Create support tickets referencing services belonging to other users - Potentially cause support staff to interact with or review unrelated customer services The vulnerability did not allow: - Direct access to another user's service - Modification of another user's service - Retrieval of confidential service data through the vulnerable endpoint itself
AI coding agents often install or upgrade packages automatically in composer. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| paymenter/paymentercomposer | <1.5.0 | 1.5.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate paymenter/paymenter to 1.5.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPaymenter has broken object level authorization via service reference manipulation on ticket creation affects paymenter/paymenter (composer). Severity is medium. ### Summary The ticket creation endpoint accepts a user-supplied service identifier without enforcing ownership validation, allowing authenticated users to create support tickets referencing services belonging to other accounts by modifying the service ID in the request. ### Technical Details The ticket creation endpoint accepted a user-supplied service identifier without verifying ownership or authorization against the authenticated account. An attacker could modify the service ID value in the client-side request and successfully create a ticket associated with another user's service. The vulnerability required authentication and did not provide direct access to service contents or customer data. However, referenced service information could become visible to support personnel handling the ticket. ### Impact Successful exploitation could allow an authenticated user to: - Create support tickets referencing services belonging to other users - Potentially cause support staff to interact with or review unrelated customer services The vulnerability did not allow: - Direct access to another user's service - Modification of another user's service - Retrieval of confidential service data through the vulnerable endpoint itself
AI coding agents often install or upgrade packages automatically in composer. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| paymenter/paymentercomposer | <1.5.0 | 1.5.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard