Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV

CVE-2013-6374 build-failure-analyzer

Fix: jenkinsci/build-failure-analyzer-plugin@cf20a8d

CVE-2013-6374 is a Cross-site Scripting (XSS) vulnerability in com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer. A fix is available for com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer — see the affected versions and patch details below.

Jenkins Build Failure Analyzer Plugin allows Cross-Site Scripting (XSS)

Published
May 17, 2022
Updated
Mar 13, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected
com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer

Real-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

Cross-site scripting (XSS) vulnerability in the Build Failure Analyzer plugin before 1.5.1 for Jenkins allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.sonyericsson.jenkins.plugins.bfa:build-failure-analyzerall versions1.5.1com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer:1.5.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6374 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-6374 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-6374. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability in the Build Failure Analyzer plugin before 1.5.1 for Jenkins allows remote authenticated users to inject arbitrary web script or HTML via unspecified vectors.
O3 Security · Impact-Aware SCA

Is CVE-2013-6374 in your dependencies?

O3 Security finds CVE-2013-6374 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2013-6374: build-failure-analyzer XSS | O3 Security