CVE-2025-64105

{"id": "CVE-2025-64105", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-64105", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-24T13:10:09.607340Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.1, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "FOSSBilling", "product": "FOSSBilling", "versions": [{"status": "affected", "version": ">= 0.6.21, < 0.8.0"}]}]}], "published": "2026-06-23T21:16:53.927", "references": [{"url": "https://github.com/FOSSBilling/FOSSBilling/releases/tag/0.8.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-rcr8-p92p-9887", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "FOSSBilling is a billing and client management system that automates invoicing, payments, and communication for online service businesses. Versions 0.6.21 through 0.7.2 are vulnerable to IDOR through the support ticket creation workflow. By manipulating rel_id when rel_type=order, an authenticated client can create a support ticket that references another client's order they do not own. The ticketCreateForClient() method accepted rel_id without verifying order ownership for non-upgrade tasks, allowing clients to link a new ticket to another client's order by crafting the request. No cron task automatically processes cancel/upgrade requests from ticket relations; staff action is required. This affects integrity and confidentiality: staff could be misled into acting on the wrong order (e.g., cancellation or upgrade requests). While there is no client-to-client order data exposure, order IDs may appear in ticket context. This issue has been fixed in version 0.8.0."}, {"lang": "es", "value": "FOSSBilling es un sistema de facturaci\u00f3n y gesti\u00f3n de clientes que automatiza la facturaci\u00f3n, los pagos y la comunicaci\u00f3n para negocios de servicios en l\u00ednea. Las versiones 0.6.21 a la 0.7.2 son vulnerables a IDOR a trav\u00e9s del flujo de trabajo de creaci\u00f3n de tickets de soporte. Al manipular rel_id cuando rel_type=order, un cliente autenticado puede crear un ticket de soporte que hace referencia al pedido de otro cliente que no le pertenece. El m\u00e9todo ticketCreateForClient() aceptaba rel_id sin verificar la propiedad del pedido para tareas no relacionadas con actualizaciones, permitiendo a los clientes vincular un nuevo ticket al pedido de otro cliente al manipular la solicitud. Ninguna tarea cron procesa autom\u00e1ticamente las solicitudes de cancelaci\u00f3n/actualizaci\u00f3n de las relaciones de tickets; se requiere la acci\u00f3n del personal. Esto afecta la integridad y la confidencialidad: el personal podr\u00eda ser inducido a error al actuar sobre el pedido incorrecto (por ejemplo, solicitudes de cancelaci\u00f3n o actualizaci\u00f3n). Si bien no hay exposici\u00f3n de datos de pedidos de cliente a cliente, los ID de pedido pueden aparecer en el contexto del ticket. Este problema ha sido solucionado en la versi\u00f3n 0.8.0."}], "lastModified": "2026-10-12T21:10:00.227", "sourceIdentifier": "security-advisories@github.com"}