Skip to content
Fencer Intel
medium 4.3

CVE-2019-13237 json

Local file inclusion allows unauthorized access to internal resources in Alkacon OpenCms

published 7y ago modified 4mo ago also GHSA-36hf-6hp2-9g4c , EUVD-2019-0723

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.3%
EPSS 7.3% chance of exploitation in 30 days, percentile 94%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • maven org.opencms:opencms-core 11.0.1

Is CVE-2019-13237 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-47340)

Exploit prediction

7.35% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47340 Alkacon OpenCMS 10.5.x - Local File inclusion webapps, 2019-09-02
  • aetsu.github.io https://aetsu.github.io/OpenCms referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/154281/Alkacon-OpenCMS-10.5.x-Local-File-Inclusion.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 4.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.opencms:opencms-core
<11.0.1
11.0.1

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.