Quick answers
- Is CVE-2025-23207 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-23207 being exploited in the wild.
- How severe is CVE-2025-23207?
- Low severity, with a CVSS score of 3.1, published 17 January 2025.
- Which products and versions are affected?
- katex (npm) SEMVER:introduced=0.12.0,fixed=0.16.21.
- Is there a fix for CVE-2025-23207?
- Yes. katex (npm): upgrade to 0.16.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-23207 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-23207?
- Check whether you run katex (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- katex (npm): upgrade to 0.16.21 or later
npm install katex@0.16.21
Technical details
KaTeX's \htmlData command does not properly validate attribute name arguments before generating HTML output (CWE-116: Improper Encoding or Escaping of Output). This allows injection of malicious attributes through unvalidated input when rendering untrusted mathematical expressions via renderToString. The vulnerability impacts applications that enable the trust option and process user-controlled math expressions. An attacker can craft expressions that generate invalid or script-executing HTML attributes. The vulnerability affects versions 0.12.0 through 0.16.20 and is resolved in v0.16.21.
Affected products
- KaTeX KaTeX 0.12.0 to 0.16.20
Identifiers
- CVE-2025-23207
- GHSA-cg87-wmx4-v546
Timeline
- 2025-01-17: disclosed: GHSA-cg87-wmx4-v546 published
- 2025-01-17: patched: KaTeX v0.16.21 released with fix