GHSA-cv27-6wvh-8x7j - ApostropheCMS: Incomplete CVE-2026-53606: `meta http-equiv=refresh` `content` still ships `javascript:` / `data:` URLs
### Summary
CVE-2026-53606 expanded `allowedSchemesAppliedToAttributes` so named URL attributes (`action`, `formaction`, `data`, `poster`, `background`, later `ping`, `xlink:href`, …) go through `naughtyHref()`. A **URL nested inside `meta` `content`** (`http-equiv=refresh`) is not an attribute name on that list, so the embedded destination is never scheme-checked.
Default `allowedTags` still omit `meta`. Same non-default integrator config as 53606: allow `meta` plus `http-equiv` / `content`.
On **2.17.7**:
```text
sanitizeHtml(
'<meta http-equiv="refresh" content="0;url=javascript:alert(1)">',
{ allowedTags: ['meta'], allowedAttributes: { meta: ['http-equiv', 'content'] } }
)
// => <meta http-equiv="refresh" content="0;url=javascript:alert(1)" />
```
`data:text/html,…` and arbitrary `https:` destinations also survive. `formaction="javascript:…"` (53606) is stripped.
Please **Request CVE**. Credit: Finder + Reporter (`adrbogacz`).
### Details
`naughtyHref()` only runs when the attribute name is in `allowedSchemesAppliedToAttributes` (`index.js` ~385). Refresh URLs live in a `content` value of the form `0;url=…`, so the gate never fires. Adding `content` to that list wholesale would break ordinary meta `content` (description, viewport).
**Fix:** when `http-equiv` is `refresh` (case-insensitive), parse the `; url=` destination and run `naughtyHref('meta', url)`. Drop `content` (or the tag) if the URL is rejected. Leave other `meta` `content` values alone.
### PoC
Local `sanitize-html@2.17.7`. Output inspection only:
```text
node -e '
const sanitize = require("sanitize-html");
const opts = { allowedTags: ["meta"], allowedAttributes: { meta: ["http-equiv", "content"] } };
for (const html of [
"<meta http-equiv=\"refresh\" content=\"0;url=javascript:alert(1)\">",
"<meta http-equiv=\"refresh\" content=\"0;url=data:text/html,aaa\">",
"<form><button formaction=\"javascript:alert(1)\">x</button></form>",
]) {
console.log(html, "=>", sanitize(html, htm
MEDIUM
Severity & confidence
Source severitymedium
Platform severitymedium
Confidencehigh
Exploitationunknown
CVSS5.4
Affected
Vendorssanitize-htmlRed Hat
Productssanitize-html
Reporting sources (2)
GitHub Security Advisories
Red Hat - CVE Feed
Timeline & provenance
Published2026-10-20T18:15:33
Last updated2026-10-21T06:41:44
Ingested2026-10-20T18:21:26
FreshnessNEAR-REAL-TIME
Threat typeadvisory
Recommended action
Review the advisory and upgrade affected packages to the first patched version.
Next steps
- Identify affected systems in your environment.
- Apply the vendor patch or mitigation guidance.
- Review logs for indicators described in the advisory.
- Follow the affected vendor/product to track updates.
Confidence explanation
Reported by a government or cert-grade source (CISA, NCSC, NVD, ENISA, MSRC).
Source type: vendor · Original: GitHub Security Advisories