Blast Radius
october/backendReal-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
Impact
Pasting content copied from malicious websites into the Froala richeditor could result in a successful self-XSS attack.
Patches
Issue has been patched in Build 467 (v1.0.467).
Workarounds
Apply https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5 to your installation manually if unable to upgrade to Build 467.
References
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Threat Assessment
Assessed as Low given that by the nature of the attack it can only impact users that do it to themselves by copying and pasting from malicious websites.
Acknowledgements
Thanks to Michał Bentkowski of Securitum for finding the original issue in Froala and @tomaszstrojny for reporting the issue to the October CMS team.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | october/backend | ≥ 1.0.319&&< 1.0.467 | 1.0.467 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/backend. 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 october/backend to 1.0.467 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pc2-fm7p-q2vg 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 GHSA-3pc2-fm7p-q2vg 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-3pc2-fm7p-q2vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3pc2-fm7p-q2vg in your dependencies?
O3 detects GHSA-3pc2-fm7p-q2vg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.