llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Packagist · getgrav/grav

GHSA-C85G-Q5W4-FF68

Page authors can capture visitors' HTTP Basic credentials through Twig in page content

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión2.2.5
Exposición43 dDesde la divulgación, 6 oct 2026, 10:04 p. m.
Detección42 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
7 oct 26
18 nov 26
19 nov 26
7 oct 26
18 oct 26
29 oct 26
9 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-C85G-Q5W4-FF68 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

On a site where visitors authenticate with HTTP Basic credentials, a user who can only write pages could add Twig to page content that reads the Basic username and password of whoever views the page, and sends them to a host of the author's choosing. Sites that do not use HTTP Basic authentication are not affected.

Affected versions

Grav 2.0.0 through 2.2.4. From 2.0.19 Twig in page content is on by default, so every page writer can use it. On 2.0.0 to 2.0.18 only sites that had turned on `security.twig_content.process_enabled` are affected. Grav 1.7 has no content sandbox, so page authors there already have unrestricted Twig and there is no boundary for this issue to cross.

Details

Grav built the current request's `Uri` object with the visitor's Basic credentials taken from PHP's `PHP_AUTH_USER` and `PHP_AUTH_PW`, which PHP fills from the `Authorization: Basic` header. `Uri::toArray()` returned them as `user` and `pass`, and `Uri::__toString()` wrote them into the address as `user:pass@host`.

The Twig content sandbox allows `toarray` and `__tostring` on `Grav\Common\Uri`, so page content could print the credentials with `{{ uri.toarray.pass }}` or simply `{{ uri }}`, as well as through `url(uri)`, `uri|array` and `uri|yaml_encode`. The original report names `toArray()`; printing the object is enough. Placed inside an inline style that loads a background image from another host, the value is sent there when the visitor's browser loads the page.

On versions before 2.0.25 the rendered result was also stored in the shared page cache, so one visitor's credentials could be served to later visitors.

Impact

A page author learns the HTTP Basic username and password of other visitors, including administrators. This matters where each visitor has their own Basic credentials, for example a per-user htpasswd file or Basic authentication backed by LDAP or another directory, where the password may also open other systems. Where a single shared Basic password is already known to every author, nothing new is exposed.

Patches

Fixed in Grav 2.2.5. The request `Uri` no longer carries the visitor's Basic credentials, so nothing in page content or in a theme can print them. `Uri::user()` and `Uri::password()` are now empty for the current request; code that needs the Basic credentials should read them from the server variables directly. No configuration change is needed, including on sites with their own `security.twig_sandbox` allowlist.

Credits

Reported by @baeseungwon1010.

Versiones

Rangos afectados

Afectada Corregida
getgrav/grav≥ 2.0.0 < 2.2.5
2.0.0
2.2.5
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Packagistgetgrav/grav
Corregida 2.2.5 — —
Versiones corregidas2.2.5
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/getgrav/grav/security/advisories/GHSA-c85g-q5w4-ff68

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.