The management panel in Piwigo 2.9.3 has stored XSS via the name parameter in
a /ws.php?format=json request. CSRF exploitation, related to CVE-2017-10681,
may be possible.
From discussion with developer:
The best one would be to add a required parameter pwg_token, but it would break
remote apps (like the iOS app) which is more a problem than a solution. So we will
escape any JS in the "name" parameter.
When you fix this vulnerability could you mention CVE in commit message, thank you.
https://nvd.nist.gov/vuln/detail/CVE-2018-7722
> The management panel in Piwigo 2.9.3 has stored XSS via the name parameter in
> a /ws.php?format=json request. CSRF exploitation, related to CVE-2017-10681,
> may be possible.
From discussion with developer:
> The best one would be to add a required parameter pwg_token, but it would break
> remote apps (like the iOS app) which is more a problem than a solution. So we will
> escape any JS in the "name" parameter.
When you fix this vulnerability could you mention CVE in commit message, thank you.
<!-- github-sync-id:325607029 -->
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.
https://nvd.nist.gov/vuln/detail/CVE-2018-7722
From discussion with developer:
When you fix this vulnerability could you mention CVE in commit message, thank you.
@plegall can we fix this also in 2.9.4?
@fgeek yes, it was a bit more complicated to fix, compared to #872
Great. Thank you for your efforts once again.