dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13472

MEDIUM · 5.3 CVSS v4.0 Published 2025-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

The BlazeMeter Jenkins Plugin before version 4.27 allowed any authenticated Jenkins user to view sensitive resource information (credential IDs, bzm workspace names, and bzm project IDs) displayed in dropdown menus on the Jenkins UI, without requiring proper permissions. This exposed potentially sensitive identifiers to unauthorized users.

MitigationUpgrade BlazeMeter Jenkins Plugin to version 4.27 or later, which implements proper permission checks to restrict visibility of credential IDs, workspaces, and project IDs to only authorized users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if BlazeMeter Jenkins Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'BlazeMeter' in the list, or inspect the $JENKINS_HOME/plugins/ directory for a blazemeter folder.
    Affected if The blazemeter plugin folder or entry exists in Jenkins.
  2. Determine the installed version of BlazeMeter Plugin
    In Jenkins UI, find the BlazeMeter entry in Manage Plugins > Installed and note the Version column. Alternatively, inspect the file $JENKINS_HOME/plugins/blazemeter/WEB-INF/lib/ and check the MANIFEST.MF file inside the plugin JAR for the Plugin-Version attribute.
    Affected if The version is present and can be compared to the fixed version.
  3. Compare installed version to the fixed version 4.27
    Compare the version found in the previous step against 4.27 using standard version comparison (e.g., 4.26, 4.25, 4.0 are all below 4.27).
    Affected if The installed version is numerically less than 4.27 (e.g., 4.26 or earlier).
  4. Verify any authenticated user can access BlazeMeter dropdown menus
    Log in with a Jenkins user account that has only minimal permissions (such as Overall/Read access) and navigate to a job configuration page or BlazeMeter-related UI section to see if dropdown menus displaying credential IDs, workspace names, or project IDs are visible without having explicit BlazeMeter permissions.
    Affected if Dropdown menus showing credential IDs, workspace names, or project IDs are visible to a user without BlazeMeter-specific permissions.

A Jenkins environment is affected if the BlazeMeter plugin is installed with a version lower than 4.27 and any authenticated user (without BlazeMeter-specific permissions) can view sensitive dropdown menus containing credential IDs, workspace names, or project IDs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BlazeMeter Jenkins Plugin to version 4.27 or later, which implements proper permission checks to restrict visibility of credential IDs, workspaces, and project IDs to only authorized users.

Recommended fix Moderate confidence

BlazeMeter Jenkins Plugin version 4.27 or later

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Locate the BlazeMeter (bzm) Jenkins Plugin in the list
  5. If an update is available, click 'Update' to upgrade to version 4.27 or later
  6. Alternatively, if the plugin is not showing an update, download BlazeMeter Plugin version 4.27 or newer from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'
  7. Restart Jenkins to complete the installation

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13472 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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