CVE-2023-2980
Abstrium Pydio Cells 4.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-2980 is a medium-severity Resource Injection (CWE-99) vulnerability in Abstrium Pydio Cells. Its CVSS base score is 6.3 (Medium).
Operationally, ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1562
Vulnerability Data
A vulnerability classified as critical was found in Abstrium Pydio Cells 4.2.0. This vulnerability affects unknown code of the component User Creation Handler. The manipulation leads to improper control of resource identifiers. The attack can be initiated remotely. The exploit…
more
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 of this vulnerability is VDB-230212.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Developer assessments and testing (including injection-focused techniques) identify improper neutralization of special elements, and the verifiable flaw remediation corrects them pre-deployment.
Identifies indicators of injection attacks (command, SQL, LDAP, etc.) via anomaly and attack monitoring.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, testing (scans/penetration), and developer training that reduce the chance of introducing resource injection flaws, but does not guarantee their absence at runtime and leaves a bounded remainder (e.g. incomplete enforcement of input restrictions or flaws in non-development phases).
Application security requirements explicitly call for controls on external identifiers used to access resources.
A.8.27 mandates security-by-design principles (e.g. distrust external input, least privilege, fail securely, data validation/sanitization) and design reviews that can stop resource injection from reaching production, but this is only a minority slice of CWE-99 because the control sets process expectations rather than mandating any specific runtime enforcement mechanism that would block exploitation of every possible identifier misuse.
Secure coding standards require strict validation and whitelisting of all resource identifiers before use.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-99, a class-level weakness, and none of its children carries one either.
- No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.