CVE-2025-54136

{"id": "CVE-2025-54136", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.2, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.2}]}, "published": "2025-08-02T00:15:25.290", "references": [{"url": "https://github.com/cursor/cursor/security/advisories/GHSA-24mc-g4xr-4395", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-78"}]}], "descriptions": [{"lang": "en", "value": "Cursor is a code editor built for programming with AI. In versions 1.2.4 and below, attackers can achieve remote and persistent code execution by modifying an already trusted MCP configuration file inside a shared GitHub repository or editing the file locally on the target's machine. Once a collaborator accepts a harmless MCP, the attacker can silently swap it for a malicious command (e.g., calc.exe) without triggering any warning or re-prompt. If an attacker has write permissions on a user's active branches of a source repository that contains existing MCP servers the user has previously approved, or allows an attacker has arbitrary file-write locally, the attacker can achieve arbitrary code execution. This is fixed in version 1.3."}, {"lang": "es", "value": "Cursor es un editor de c\u00f3digo creado para programar con IA. En las versiones 1.2.4 y anteriores, los atacantes pueden lograr la ejecuci\u00f3n remota y persistente de c\u00f3digo modificando un archivo de configuraci\u00f3n MCP ya confiable dentro de un repositorio compartido de GitHub o edit\u00e1ndolo localmente en el equipo objetivo. Una vez que un colaborador acepta un MCP inofensivo, el atacante puede reemplazarlo silenciosamente por un comando malicioso (por ejemplo, calc.exe) sin generar ninguna advertencia ni solicitud. Si un atacante tiene permisos de escritura en las ramas activas de un usuario de un repositorio de origen que contiene servidores MCP existentes que el usuario ha aprobado previamente, o permite que un atacante escriba archivos arbitrariamente localmente, puede lograr la ejecuci\u00f3n de c\u00f3digo arbitrario. Esto se solucion\u00f3 en la versi\u00f3n 1.3."}], "lastModified": "2025-08-04T15:06:15.833", "sourceIdentifier": "security-advisories@github.com"}