File and Path Handling

Every one of the 7 is a mark on the map. Named now: 1 to 7, most at risk first.

1. An issue was discovered in OFCMS before 1.1.3. Remote attackers can execute arbitrary code because blocking of .jsp and .jspx files does not consider (for example) file.jsp::$DATA…CVE-2019-9617Ofcms Project · 2.7% likely

   CWE-434

2. An issue was discovered in OFCMS before 1.1.3. Remote attackers can execute arbitrary code because blocking of .jsp and .jspx files does not consider (for example) file.jsp::$DATA…CVE-2019-9613Ofcms Project · 2.7% likely

   CWE-434

3. An issue was discovered in OFCMS before 1.1.3. Remote attackers can execute arbitrary code because blocking of .jsp and .jspx files does not consider (for example) file.jsp::$DATA…CVE-2019-9612Ofcms Project · 2.7% likely

   CWE-434

4. An issue was discovered in OFCMS before 1.1.3. Remote attackers can execute arbitrary code because blocking of .jsp and .jspx files does not consider (for example) file.jsp::$DATA…CVE-2019-9609Ofcms Project · 2.7% likely

   CWE-434

5. An issue was discovered in OFCMS before 1.1.3. Remote attackers can execute arbitrary code because blocking of .jsp and .jspx files does not consider (for example) file.jsp::$DATA…CVE-2019-9608Ofcms Project · 2.7% likely

   CWE-434

6. An issue was discovered in OFCMS before 1.1.3. It allows admin/cms/template/getTemplates.html?res_path=res directory traversal, with ../ in the dir parameter, to write arbitrary c…CVE-2019-9611Ofcms Project · 1.4% likely

   CWE-22

7. An issue was discovered in OFCMS before 1.1.3. It has admin/cms/template/getTemplates.html?res_path=res&up_dir=../ directory traversal, related to the getTemplates function in Tem…CVE-2019-9610Ofcms Project · 1.4% likely

   CWE-22

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.