Jenkins Warnings Next Generation Plugin cross-site request forgery vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2019-1003008: 1.19% estimated exploitation activity in the next 30 days; percentile 67.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Warnings Next Generation Plugin has a form validation HTTP endpoint used to validate a Groovy script through compilation, which was not subject to sandbox protection. The endpoint checked for the Overall/RunScripts permission, but did not require POST requests, so it was vulnerable to cross-site request forgery (CSRF). This allowed attackers to execute arbitrary code on the Jenkins controller by applying AST transforming annotations such as @Grab to source code elements. The affected HTTP endpoint now applies a safe Groovy compiler configuration preventing the use of unsafe AST transforming annotations. Additionally, the form validation HTTP endpoint now requires that requests be sent via POST to prevent CSRF.

Published by the source

13 May 2022, 01:31 UTC

Last modified by the source

25 Oct 2023, 23:03 UTC

Source last checked

26 Oct 2026, 16:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-whf8-3h58-2w9f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1003008

Advisory: Jenkins Warnings Next Generation Plugin cross-site request forgery vulnerability
IDs: CVE-2019-1003008, GHSA-whf8-3h58-2w9f
Record: https://patchnext.com/advisories/cve-2019-1003008 (revision 1, source checked 26 Oct 2026, 16:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.plugins:warnings-ng: affected <= 2.1.1

## Suggested inspection (read-only)
- Maven io.jenkins.plugins:warnings-ng: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.jenkins.plugins:warnings-ng.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-whf8-3h58-2w9f (GitHub-reviewed advisory GHSA-whf8-3h58-2w9f lists affected ranges: Maven io.jenkins.plugins:warnings-ng >=0 <=2.1.1)

Commands are suggestions: review each one before running it.