Skip to content

Unescaped GET parameters can be used to trick user to visit a malicious website.

Low
xenocrat published GHSA-h7h4-mj4g-gvc4 Jan 12, 2025

Package

chyrp-lite

Affected versions

<= 2024.03

Patched versions

2025.01

Description

Summary

Incomplete HTML sanitization on the pretty error page can be used to inject an iframe or other unwanted HTML content on the website. This injected content could then be used to direct the user to a fake "solution" to the error, with a malicious URL as the destination. The injection source is the admin_help route responder for help articles that accepts arbitrary GET request input and does not adequately sanitize it before passing it on to the Twig template engine.

Impact

This is not a stored XSS. The pretty error page provides no access to confidential data. However the XSS could be used to trick unsuspecting webmasters and/or visitors into trusting a malicious third-party website. The victim could be fooled into entering credentials into a fake login form for the purpose of credential theft, or redirected to a scam website.

Patches

Chyrp Lite "Boreal" v2025.01 resolves this issue by making the following changes:

  • HTML on error pages is limited to a subset of tags that are considered safe.
  • The admin_help route responder now strips < and > from the GET request.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits