Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-q9w4-w667-qqj4

MEDIUM

ckeditor-wordcount-plugin vulnerable to Cross-site Scripting in Source Mode of Editor

Also known asCVE-2023-37905
Published
Jul 10, 2023
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk38th percentile-0.14%
0.00%0.38%0.75%1.13%0.5%0.5%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
📦ckeditor-wordcount-plugin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Problem

It has been discovered that the ckeditor-wordcount-plugin plugin for CKEditor4 is susceptible to cross-site scripting when switching to the source code mode.

Solution

Update to version 1.17.12 of the ckeditor-wordcount-plugin plugin.

Credits

  • @sypets for reporting this finding to the TYPO3 Security Team
  • @ohader for fixing the issue on behalf of the TYPO3 Security Team

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmckeditor-wordcount-pluginall versions1.17.12

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckeditor-wordcount-plugin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ckeditor-wordcount-plugin to 1.17.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q9w4-w667-qqj4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-q9w4-w667-qqj4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q9w4-w667-qqj4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem It has been discovered that the `ckeditor-wordcount-plugin` plugin for CKEditor4 is susceptible to cross-site scripting when switching to the source code mode. ### Solution Update to version 1.17.12 of the `ckeditor-wordcount-plugin` plugin. ### Credits * @sypets for reporting this finding to the TYPO3 Security Team * @ohader for fixing the issue on behalf of the TYPO3 Security Team
O3 Security · Impact-Aware SCA

Is GHSA-q9w4-w667-qqj4 in your dependencies?

O3 detects GHSA-q9w4-w667-qqj4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.