As you can see a user-controlled input $_GET['section'] ($filename) is being sent to die() - printing out without no sanitization, this could result in cross-site scripting because die() prints out content just like echo() before exit.
Fix: do htmlentities($filename);
In Piwigo/admin/plugin.php
```
32: $sections = explode('/', $_GET['section']);
59: $filename = PHPWG_PLUGINS_PATH . implode('/', $sections);
66: die ('Missing file ' . $filename);
```
As you can see a user-controlled input $_GET['section'] ($filename) is being sent to die() - printing out without no sanitization, this could result in cross-site scripting because die() prints out content just like echo() before exit.
Fix: do htmlentities($filename);
<!-- github-sync-id:196307456 -->
So only Piwigo administrators can exploit this "security issue". Is that really a problem?
earlier in this file, you can find:
```
check_status(ACCESS_ADMINISTRATOR);
```
So only Piwigo administrators can exploit this "security issue". Is that really a problem?
<!-- github-comment-id:268242347 -->
should be. because attacker would only need to give the admin a malicious xss link, and when authorized admin visits it, check_status(ACCESS_ADMINISTRATOR); will return to true. so yes it is as dangerous.
should be. because attacker would only need to give the admin a malicious xss link, and when authorized admin visits it, check_status(ACCESS_ADMINISTRATOR); will return to true. so yes it is as dangerous.
<!-- github-comment-id:268256015 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In Piwigo/admin/plugin.php
As you can see a user-controlled input $_GET['section'] ($filename) is being sent to die() - printing out without no sanitization, this could result in cross-site scripting because die() prints out content just like echo() before exit.
Fix: do htmlentities($filename);
earlier in this file, you can find:
So only Piwigo administrators can exploit this "security issue". Is that really a problem?
should be. because attacker would only need to give the admin a malicious xss link, and when authorized admin visits it, check_status(ACCESS_ADMINISTRATOR); will return to true. so yes it is as dangerous.
Use CVE-2016-10083 for this.