How severe is CVE-2025-13472?

No CVSS score has been assigned to CVE-2025-13472 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-13472?

CVE-2025-13472 affects the following packages: com.blazemeter.plugins:BlazeMeterJenkinsPlugin (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-13472?

Update com.blazemeter.plugins:BlazeMeterJenkinsPlugin to 4.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13472 is resolved across your whole dependency graph.

How do I detect CVE-2025-13472 in my Maven dependencies?

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

How do I mitigate CVE-2025-13472 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-13472 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-13472 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-13472?

CVE-2025-13472 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-13472?

CVE-2025-13472 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-13472 published, and has it been updated?

CVE-2025-13472 was published on December 3, 2025 and was last updated on December 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-13472 — BlazeMeterJenkinsPlugin

Fix: jenkinsci/blazemeter-plugin@9fe5ed7

CVE-2025-13472 is a CWE-862 vulnerability in com.blazemeter.plugins:BlazeMeterJenkinsPlugin. A fix is available for com.blazemeter.plugins:BlazeMeterJenkinsPlugin — see the affected versions and patch details below.

BlazeMeter Jenkins Plugin is Missing Authorization for Available Resources

Published

Dec 3, 2025

Updated

Dec 3, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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-2025-13472.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.blazemeter.plugins:BlazeMeterJenkinsPlugin

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

A fix was made in BlazeMeter Jenkins Plugin version 4.27 to allow users only with certain permissions to see the list of available resources like credential IDs, bzm workspaces and bzm project Ids. Prior to this fix, anyone could see this list as a dropdown on the Jenkins UI.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.blazemeter.plugins:BlazeMeterJenkinsPlugin`	all versions	4.27`com.blazemeter.plugins:BlazeMeterJenkinsPlugin:4.27`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.blazemeter.plugins:BlazeMeterJenkinsPlugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.blazemeter.plugins:BlazeMeterJenkinsPlugin to 4.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-13472 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-13472 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works