GHSA-3h6j-9x8m-rg3g Graby has stored XSS via iframe srcdoc Attribute in htmLawed Sanitization Config

Not scored Published

Stored XSS in Graby library allows arbitrary JavaScript execution via unsanitized iframe srcdoc attributes when content is rendered raw.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is GHSA-3h6j-9x8m-rg3g?

GHSA-3h6j-9x8m-rg3g is a cross-site scripting vulnerability in j0k3r/graby, published on 31 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Summary

Graby's cleanupXss() function configures htmLawed with conflicting settings: safe=1 (which removes <iframe>) combined with 'elements' => '*+iframe-meta' (which re-enables <iframe>). htmLawed does not sanitize the srcdoc attribute, allowing injection of arbitrary JavaScript that executes when the content is rendered via |raw in templates.

Root Cause

src/Graby.php lines 1038-1048:

htmLawed($html, [
    'safe' => 1,                    // removes <iframe>
    'elements' => '*+iframe-meta',  // re-adds <iframe>, overrides safe=1
    'deny_attribute' => 'style',    // srcdoc is NOT denied
]);

The safe=1 and +iframe combination is a conflict: safe mode is designed to strip dangerous elements, but the elements override re-enables <iframe> without also blocking the dangerous srcdoc attribute.

Proof of Concept

Input to cleanupXss():

<iframe srcdoc="<script>alert(document.domain)</script>"></iframe>

Output (unchanged — htmLawed passes it through):

<iframe srcdoc="<script>alert(document.domain)</script>"></iframe>

When rendered via {{ content|raw }} in a template, srcdoc executes in an about:srcdoc frame with the same origin as the page. Confirmed via Puppeteer/Chromium headless: alert(document.domain) fires.

Validated on Wallabag (which uses Graby) via Docker: entry created via API with iframe-only content body triggers Readability failure → falls through to cleanupXss() path.

Impact

  • Stored XSS in any application rendering Graby-sanitized content via |raw
  • In Wallabag: affects both authenticated views and public share pages (unauthenticated)
  • No CSP headers in default Wallabag config — no secondary mitigation

Suggested Fix

Either remove +iframe from the elements config to keep iframes blocked:

'elements' => '*-iframe-meta',

Or explicitly deny the srcdoc attribute:

'deny_attribute' => 'style srcdoc',

Credit

Discovered by @tikket1, 2026-03-25. Redirected from wallabag/wallabag advisory by @j0k3r.

Which versions are affected by GHSA-3h6j-9x8m-rg3g?

2 open source packages ship an affected version, including j0k3r/graby.

PackageAffectedFixed in
j0k3r/graby PackagistAll versions2.5.1
j0k3r/graby PackagistAll versions2.5.1

How do I fix GHSA-3h6j-9x8m-rg3g?

Upgrade j0k3r/graby to 2.5.1 or later.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is GHSA-3h6j-9x8m-rg3g being exploited?

There is no known exploitation of GHSA-3h6j-9x8m-rg3g in the wild and no public exploit code.

Sources

Is GHSA-3h6j-9x8m-rg3g in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free