CVE-2026-32277 is a high-severity (CVSS 8.7) Cross-site Scripting (XSS) vulnerability in opensource-workshop/connect-cms. O3 Security confirms whether CVE-2026-32277 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Connect-CMS has DOM-based Cross-Site Scripting (XSS) in the Cabinet Plugin List View
Real-World Exposure
opensource-workshop/connect-cms🐘opensource-workshop/connect-cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Connect-CMS is a content management system. In versions 1.35.0 through 1.41.0 and 2.35.0 through 2.41.0, a DOM-based Cross-Site Scripting (XSS) issue exists in the Cabinet Plugin list view. Versions 1.41.1 and 2.41.1 contain a patch.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | opensource-workshop/connect-cms | ≥ 1.35.0&&< 1.41.1 | 1.41.1 |
| 🐘Packagist | opensource-workshop/connect-cms | ≥ 2.35.0&&< 2.41.1 | 2.41.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for opensource-workshop/connect-cms. 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.
Fix
Update opensource-workshop/connect-cms to 1.41.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32277 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2026-32277 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 CVE-2026-32277. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32277 in your dependencies?
O3 detects CVE-2026-32277 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.