GHSA-X93Q-X9PC-W5HW
Vulnerability from github – Published: 2026-06-22 20:30 – Updated: 2026-06-22 20:30Summary
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
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "paymenter/paymenter"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.5.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-44585"
],
"database_specific": {
"cwe_ids": [
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-22T20:30:16Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Summary\nThe 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.\n\n### Technical Details\n\nThe 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\u0027s service.\n\nThe 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.\n\n### Impact\n\nSuccessful exploitation could allow an authenticated user to:\n- Create support tickets referencing services belonging to other users\n- Potentially cause support staff to interact with or review unrelated customer services\n\nThe vulnerability did not allow:\n- Direct access to another user\u0027s service\n- Modification of another user\u0027s service\n- Retrieval of confidential service data through the vulnerable endpoint itself",
"id": "GHSA-x93q-x9pc-w5hw",
"modified": "2026-06-22T20:30:16Z",
"published": "2026-06-22T20:30:16Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Paymenter/Paymenter/security/advisories/GHSA-x93q-x9pc-w5hw"
},
{
"type": "PACKAGE",
"url": "https://github.com/Paymenter/Paymenter"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Paymenter has broken object level authorization via service reference manipulation on ticket creation"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.