CVE-2023-32998 — jenkinsci-appspider-plugin
MEDIUMCVE-2023-32998 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in com.rapid7:jenkinsci-appspider-plugin. A fix is available for com.rapid7:jenkinsci-appspider-plugin — see the affected versions and patch details below.
Jenkins AppSpider Plugin Cross-Site Request Forgery vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-32998.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.rapid7:jenkinsci-appspider-pluginReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A cross-site request forgery (CSRF) vulnerability in Jenkins AppSpider Plugin 1.0.15 and earlier allows attackers to connect to an attacker-specified URL and send an HTTP POST request with a JSON payload consisting of attacker-specified credentials.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.rapid7:jenkinsci-appspider-plugin | all versions | 1.0.16com.rapid7:jenkinsci-appspider-plugin:1.0.16 |
Affected Products
appspiderjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.rapid7:jenkinsci-appspider-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.rapid7:jenkinsci-appspider-plugin to 1.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32998 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-32998 in your dependencies?
Find it across Maven, including transitive dependencies.