CVE-2016-0784 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.apache.openmeetings:openmeetings-install. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.openmeetings:openmeetings-install — see the affected versions and patch details below.
Apache OpenMeetings Directory Traversal vulnerability
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
org.apache.openmeetings:openmeetings-installReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Directory traversal vulnerability in the Import/Export System Backups functionality in Apache OpenMeetings before 3.1.1 allows remote authenticated administrators to write to arbitrary files via a .. (dot dot) in a ZIP archive entry.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.openmeetings:openmeetings-install | ≥ 1.9.0&&< 3.1.1 | 3.1.1org.apache.openmeetings:openmeetings-install:3.1.1 |
Affected Products
openmeetingsapacheResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache OpenMeetings 1.9.x < 3.1.0 - '.ZIP' File Directory Traversal
by Andreas Lindh · Mar 31, 2016
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.openmeetings:openmeetings-install, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.openmeetings:openmeetings-install to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0784 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2016-0784 in your dependencies?
Find it across Maven, including transitive dependencies.