Read the docs
TI-2020-02078 Aliases CVE-2020-2201GHSA-f799-hfg3-48jp

Cross-site scripting in Jenkins Sonargraph Integration Plugin

Priority LOW 26CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Required
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-79.

Summary

Jenkins Sonargraph Integration Plugin 3.0.0 and earlier does not escape the file path for the Log file field form validation, resulting in a stored cross-site scripting vulnerability.

Why it matters now

EPSS 0.00735 54th percentileScored 2026-11-07
Fix Fixed org.jenkins-ci.plugins:sonargraph-integration (Maven): 3.0.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
JenkinsJenkins Sonargraph Integration Pluginup to 3.0.0—No fix listedCNA
—org.jenkins-ci.plugins:sonargraph-integration (Maven)before 3.0.13.0.1Patch availableGHSA-f799-hfg3-48jp
  • Jenkins Sonargraph Integration Plugin VendorJenkins Affected up to 3.0.0 Fixed in — No fix listed CNA
  • org.jenkins-ci.plugins:sonargraph-integration (Maven) Vendor— Affected before 3.0.1 Fixed in 3.0.1 Patch available GHSA-f799-hfg3-48jp

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:jenkins:sonargraph_integration:*:*:*:*:*:jenkins:*:*up to 3.0.0VulnerableJenkins
  • cpe:2.3:a:jenkins:sonargraph_integration:*:*:*:*:*:jenkins:*:* Versions up to 3.0.0 Vulnerable ·Jenkins

Remediation

  • Fix · GHSA-f799-hfg3-48jp org.jenkins-ci.plugins:sonargraph-integration (Maven) Fixed in 3.0.1 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2020-2201
  2. 2026-10-03 Alias added: GHSA-f799-hfg3-48jp

References

Advisory 3

Other 1

  • TI-2023-17591 Cross-site scripting in Jenkins Sonargraph Integration Plugin CVSS 3.1MEDIUM 5.4

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences