dbcve.org
Html SanitizerApplication · TYPO3

CVE-2022-23499

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HTML sanitizer is written in PHP, aiming to provide XSS-safe markup based on explicitly allowed tags, attributes and values. In versions prior to 1.5.0 or 2.1.1, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized due to a parsing issue in the upstream package masterminds/html5. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. The upstream package masterminds/html5 provides HTML raw text elements (`script`, `style`, `noframes`, `noembed` and `iframe`) as DOMText nodes, which were not processed and sanitized further. None of the mentioned elements were defined in the default builder configuration, that's why only custom behaviors, using one of those tag names, were vulnerable to cross-site scripting. This issue has been fixed in versions 1.5.0 and 2.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The typo3/html-sanitizer library has an XSS bypass vulnerability caused by a parsing issue in the upstream masterminds/html5 package. Raw text elements (script, style, noframes, noembed, iframe) are incorrectly parsed as DOMText nodes instead of proper HTML elements, bypassing sanitization. Only custom behaviors using these specific tag names are vulnerable since they aren't in the default configuration.

MitigationUpgrade typo3/html-sanitizer to version 1.5.0 or 2.1.1 or later to patch the parsing issue in the upstream dependency.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Html SanitizerApplication
Affected:>= 1.0.0, <= 1.0.7>= 2.0.0, < 2.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate typo3/html-sanitizer library
    Check your project's composer.json or vendor directory for the typo3/html-sanitizer package. Run `composer show typo3/html-sanitizer` to see the installed version.
    Affected if The library is not installed or cannot be found, this CVE does not apply.
  2. Compare installed version to affected ranges
    Check if the installed version is >= 1.0.0 AND <= 1.0.7, OR >= 2.0.0 AND < 2.1.1.
    Affected if The version falls within these ranges, the library is potentially vulnerable.
  3. Identify custom behavior configurations
    Search your project for PHP or YAML configuration files that define custom TagBehavior classes for the html-sanitizer, particularly looking for entries that define allowed tags or custom processors.
    Affected if No custom behaviors are defined, the default configuration is used which is not affected by this vulnerability.
  4. Check for vulnerable tag usage in custom behaviors
    In custom behavior configurations, examine whether the tags script, style, noframes, noembed, or iframe are explicitly allowed or have custom processing rules defined.
    Affected if Custom behaviors explicitly handle any of these five tags (script, style, noframes, noembed, iframe), the XSS bypass may be exploitable.

Your environment is affected if typo3/html-sanitizer version is between 1.0.0-1.0.7 or 2.0.0-2.1.0 AND custom sanitizer behaviors include processing for script, style, noframes, noembed, or iframe tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade typo3/html-sanitizer to version 1.5.0 or 2.1.1 or later to patch the parsing issue in the upstream dependency.

Recommended fix High confidence

Version 1.5.0 for 1.x branch; Version 2.1.1 for 2.x branch

  1. Identify the current version of typo3/html-sanitizer in use (check composer.json or lock file)
  2. If using version 1.x (>= 1.0.0, <= 1.0.7): upgrade to version 1.5.0 or later
  3. If using version 2.x (>= 2.0.0, < 2.1.1): upgrade to version 2.1.1 or later
  4. Run composer update typo3/html-sanitizer to apply the upgrade
  5. Verify the upgrade was successful by checking the installed version
  6. Test the sanitizer with custom behaviors that use raw text elements (script, style, noframes, noembed, iframe) to confirm XSS protection is working
Caveat Likely minimal - this is a security fix. However, review the release notes for 1.5.0 and 2.1.1 to check for any behavior changes that might affect custom tag configurations.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Html Sanitizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23499 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data