← Back to results
Vulnerability record · public intelligence
CVE-2024-22048
MEDIUM

govuk_tech_docs vulnerable to unescaped HTML on search results page

Published Jan 4, 2024 · Updated Oct 23, 2026 · Also known as GHSA-x2xw-hw8g-6773

Severity · CVSSMEDIUM · 6.1
Known exploitationNot listed
EPSS / likelihood0.50%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

govuk_tech_docs vulnerable to unescaped HTML on search results page

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Pages that are indexed in search results have their entire contents indexed, including any HTML code snippets. These HTML snippets would appear in the search results unsanitised, so it was possible to render arbitrary HTML or run arbitrary scripts.

Potential impact

Pages that are indexed in search results have their entire contents indexed, including any HTML code snippets. These HTML snippets would appear in the search results unsanitised, so it was possible to render arbitrary HTML or run arbitrary scripts. This is a low risk security issue; to exploit it, an attacker would need to find a way of committing malicious code to a page indexed by a site that uses tech-docs-gem (which are typically not editable by untrusted users). Their code would also be limited by the relatively short length that's rendered in the corresponding search result. Nevertheless, the XSS would then be triggerable by visiting a pre-constructed URL (/search/index.html?q=some+search+term), which users could be tricked into clicking on through social engineering.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-x2xw-hw8g-6773

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Source repository ↗
  5. vulncheck.com ↗

Record history

Published Jan 4, 2024 · Last refreshed Oct 23, 2026