GHSA-36hf-6hp2-9g4c
MEDIUMGHSA-36hf-6hp2-9g4c is a medium-severity (CVSS 4.3) Path Traversal vulnerability in org.opencms:opencms-core. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-36hf-6hp2-9g4c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Local file inclusion allows unauthorized access to internal resources in Alkacon OpenCms
Real-World Exposure
org.opencms:opencms-coreReal-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
In Alkacon OpenCms 10.5.4 and 10.5.5, there are multiple resources vulnerable to Local File Inclusion that allow an attacker to access server resources: clearhistory.jsp, convertxml.jsp, group_new.jsp, loginmessage.jsp, xmlcontentrepair.jsp, and /system/workplace/admin/history/settings/index.jsp.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opencms:opencms-core | all versions | 11.0.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Alkacon OpenCMS 10.5.x - Local File inclusion
by Aetsu · Sep 2, 2019
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencms:opencms-core. 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 org.opencms:opencms-core to 11.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-36hf-6hp2-9g4c 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-36hf-6hp2-9g4c 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-36hf-6hp2-9g4c. 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-36hf-6hp2-9g4c in your dependencies?
O3 detects GHSA-36hf-6hp2-9g4c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.