Warnings Next GenerationApplication · Jenkins
CVE-2019-10325
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA cross-site scripting vulnerability in Jenkins Warnings NG Plugin 5.0.0 and earlier allowed attacker with Job/Configure permission to inject arbitrary JavaScript in build overview pages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored cross-site scripting (XSS) vulnerability in Jenkins Warnings NG Plugin version 5.0.0 and earlier allows authenticated users with Job/Configure permission to inject arbitrary JavaScript code that executes when viewing build overview pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Warnings Next GenerationApplication
<= 5.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Warnings NG Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Warnings NG' or 'Warnings Next Generation', or inspect the plugin filesystem at $JENKINS_HOME/plugins/ for a directory named warnings-ng or similarAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Manage Plugins > Installed view, locate the Warnings NG plugin and note the version number displayed in the Version columnAffected if The displayed version is 5.0.0 or lower
-
Confirm plugin is active on any jobsNavigate to a Jenkins job configuration page and look for a 'Record compiler warnings' or 'Warnings NG' post-build step or publisher, or search job configurations for 'io.jenkins.plugins.warningsng' in $JENKINS_HOME/jobs/Affected if Any job has the Warnings NG recorder configured and enabled
-
Identify users with Job/Configure permissionReview Jenkins matrix-based security or project-based authorization settings at Manage Jenkins > Configure Global Security, and check which users or groups are granted the Job/Configure permissionAffected if Any user or group beyond administrators has Job/Configure permission, enabling the XSS vector
You are affected if the Warnings NG Plugin is installed at version 5.0.0 or lower and is actively used in at least one Jenkins job, especially when users with Job/Configure permission exist.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Warnings NG Plugin to a version newer than 5.0.0; until then, strictly limit and audit users with Job/Configure permissions.
Fix this in Warnings Next Generation
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data