CVE-2023-2981 — cells
MEDIUMCVE-2023-2981 is a medium-severity (CVSS 5.4) CWE-80 vulnerability in github.com/pydio/cells. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/pydio/cells — see the affected versions and patch details below.
go package pydio cells vulnerable to cross-site scripting
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/pydio/cellsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability, which was classified as problematic, has been found in Abstrium Pydio Cells 4.2.0. This issue affects some unknown processing of the component Chat. The manipulation leads to basic cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 4.2.1 is able to address this issue. It is recommended to upgrade the affected component. The identifier VDB-230213 was assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pydio/cells | all versions | 4.2.1go get github.com/pydio/cells@v4.2.1 |
Affected Products
pydio cellsabstriumResearch 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 github.com/pydio/cells, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pydio/cells to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2981 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.
Frequently Asked Questions
Is CVE-2023-2981 in your dependencies?
Find it across Go, including transitive dependencies.