DEMON1A/WEngine

Issues

• [WEngine] TemplatesEngine is way too sensitive to spaces

  #10 opened 2 years ago by DEMON1A
  1

• [WEngine] Documents are totally outdated and missing important information

  #12 opened 2 years ago by DEMON1A
  0

• [WEngine] Add POST method support to the web server

  #11 opened 2 years ago by DEMON1A
  0

• [WEngine] Weak hashing algorithm -sha256- is being used on the createuser class

  #9 opened 2 years ago by DEMON1A
  0

• LFI at the static files handler using backslash to bypass protection

  #8 opened 2 years ago by DEMON1A
  1

• Broken `urlencode` syntax on the templateEngine due to invalid function used.

  #7 opened 4 years ago by DEMON1A
  1

• WEngine CORs system doesn't support subdomains on allowed domains.

  #6 opened 4 years ago by DEMON1A
  1

• Stored-XSS on logs viewer using all values due to the default content-type usage.

  #5 opened 4 years ago by DEMON1A
  1

• Cors credentials headers is set even if cors isn't enabled at all.

  #4 opened 4 years ago by DEMON1A
  1

• Two content-type headers are getting send on the server response to GET reqeusts.

  #3 opened 4 years ago by DEMON1A
  1

• WEngine settings can result in CR LF injection and Stored-XSS using new lines.

  #2 opened 4 years ago by DEMON1A
  1

• Some responses comes without `content-type` header making the server respond with `text/plain`

  #1 opened 4 years ago by DEMON1A
  2