CVE-2021-41252

{"id": "CVE-2021-41252", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 2.1, "accessVector": "NETWORK", "vectorString": "AV:N/AC:H/Au:S/C:N/I:P/A:N", "authentication": "SINGLE", "integrityImpact": "PARTIAL", "accessComplexity": "HIGH", "availabilityImpact": "NONE", "confidentialityImpact": "NONE"}, "acInsufInfo": false, "impactScore": 2.9, "baseSeverity": "LOW", "obtainAllPrivilege": false, "exploitabilityScore": 3.9, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": true}], "cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 5.4, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 2.7, "exploitabilityScore": 2.3}, {"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.3, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.1}]}, "published": "2021-11-16T18:15:07.513", "references": [{"url": "https://github.com/getkirby/kirby/commit/25fc5c6b330442e6433c99befc688f3698c5d1fc", "tags": ["Patch", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/getkirby/kirby/releases/tag/3.5.8", "tags": ["Release Notes", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/getkirby/kirby/security/advisories/GHSA-x7j7-qp7j-hw3q", "tags": ["Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-79"}]}], "descriptions": [{"lang": "en", "value": "Kirby is an open source file structured CMS ### Impact Kirby's writer field stores its formatted content as HTML code. Unlike with other field types, it is not possible to escape HTML special characters against cross-site scripting (XSS) attacks, otherwise the formatting would be lost. If the user is logged in to the Panel, a harmful script can for example trigger requests to Kirby's API with the permissions of the victim. Because the writer field did not securely sanitize its contents on save, it was possible to inject malicious HTML code into the content file by sending it to Kirby's API directly without using the Panel. This malicious HTML code would then be displayed on the site frontend and executed in the browsers of site visitors and logged in users who are browsing the site. Attackers must be in your group of authenticated Panel users in order to exploit this weakness. Users who do not make use of the writer field are not affected. This issue has been patched in Kirby 3.5.8 by sanitizing all writer field contents on the backend whenever the content is modified via Kirby's API. Please update to this or a later version to fix the vulnerability."}, {"lang": "es", "value": "Kirby es un CMS estructurado por archivos de c\u00f3digo abierto ### Impacto: El campo writer de Kirby almacena su contenido formateado como c\u00f3digo HTML. A diferencia de otros tipos de campo, no es posible escapar los caracteres especiales de HTML contra ataques de tipo cross-site scripting (XSS), de lo contrario el formato se perder\u00eda. Si el usuario ha iniciado sesi\u00f3n en el Panel, un script da\u00f1ino puede, por ejemplo, lanzar peticiones a la API de Kirby con los permisos de la v\u00edctima. Como el campo writer no saneaba su contenido de forma segura al guardarlo, era posible inyectar c\u00f3digo HTML malicioso en el archivo de contenido al enviarlo a la API de Kirby directamente sin usar el Panel. Este c\u00f3digo HTML malicioso se mostrar\u00eda entonces en el frontend del sitio y ser\u00eda ejecutado en los navegadores de visitantes del sitio y de usuarios registrados que estuvieran navegando por el sitio. Los atacantes deben estar en su grupo de usuarios autenticados del Panel para poder explotar esta debilidad. Los usuarios que no hacen uso del campo writer no est\u00e1n afectados. Este problema ha sido parcheado en Kirby versi\u00f3n 3.5.8 saneando todo el contenido del campo escritor en el backend siempre que el contenido sea modificado por medio de la API de Kirby. Por favor, actualice a esta versi\u00f3n o a una posterior para solucionar la vulnerabilidad"}], "lastModified": "2021-11-18T17:24:29.563", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "092FA583-2B21-4F4A-8C68-43DE0C504FC8", "versionEndIncluding": "3.5.7.1", "versionStartIncluding": "3.5.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}