Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks. This allowed attackers to initiate polling of projects with a known name. While Jenkins in general does not consider polling to be a protection-worthy action as it's similar to cache invalidation, the plugin specifically adds a permission to be able to use this functionality, and this issue undermines that permission.
{
"extracted_events": [
{
"introduced": "0"
},
{
"last_affected": "1.3.1"
}
],
"cpe": "cpe:2.3:a:jenkins:poll_scm:*:*:*:*:*:jenkins:*:*",
"source": "CPE_RANGE"
}