dbcve.org
HertzbeatApplication · Apache

CVE-2025-48208

HIGH · 8.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 1.7.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache HertzBeat . The attacker needs to have an authenticated account with access, and the attack can only be triggered by crafting custom commands. A successful attack would result in arbitrary script execution. This issue affects Apache HertzBeat: through 1.7.2. Users are recommended to upgrade to version [1.7.3], which fixes the issue.

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

LDAP injection vulnerability in Apache HertzBeat allows authenticated attackers to manipulate LDAP queries through unsanitized input in custom commands, potentially achieving arbitrary script execution.

MitigationUpgrade to Apache HertzBeat version 1.7.3 or later. If immediate upgrade is not possible, implement strict input validation and parameterized LDAP queries to prevent injection.

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
HertzbeatApplication
Affected:< 1.7.3

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify HertzBeat installation and version
    Locate the HertzBeat installation directory and check the version file or use the package manager to query the installed version. Common locations include /opt/hertzbeat or the service banner if exposed via HTTP.
    Affected if The installed version is below 1.7.3
  2. Confirm custom command feature is in use
    Inspect the HertzBeat configuration for custom command definitions. Look for any custom monitoring templates, script-based checks, or command execution configurations in the web UI or config files.
    Affected if Custom commands or script-based monitoring definitions are configured
  3. Verify LDAP authentication is enabled
    Check the application configuration (typically application.yml or application.properties) for LDAP-related settings such as ldap urls, ldap base, or LDAP authentication provider configuration.
    Affected if LDAP authentication or LDAP directory queries are configured and active
  4. Check for unsanitized input in command configurations
    Review any custom command definitions for parameters that could be passed to LDAP queries without input validation. Look for placeholders or variables that accept user-supplied values.
    Affected if Custom commands accept external or user-controlled input that could be used in LDAP query contexts

You are affected if running Apache HertzBeat version below 1.7.3 with both custom command functionality and LDAP authentication or LDAP query features configured.

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
Upgrade available Upgrade to 1.7.3 or later
Fixed in 1.7.3
Interim mitigation

Upgrade to Apache HertzBeat version 1.7.3 or later. If immediate upgrade is not possible, implement strict input validation and parameterized LDAP queries to prevent injection.

Recommended fix High confidence

1.7.3

  1. Review the release notes for Apache HertzBeat version 1.7.3 to understand changes and ensure compatibility with your environment
  2. Create a backup of your current HertzBeat configuration and data
  3. Stop the running HertzBeat service
  4. Download Apache HertzBeat version 1.7.3 from the official Apache download repository
  5. Install or deploy version 1.7.3 following the standard installation process
  6. Start the HertzBeat service
  7. Verify the service is running correctly and test that the application functions as expected
  8. Confirm the LDAP injection vulnerability is resolved by ensuring custom commands cannot inject LDAP queries

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

Fix this in Hertzbeat Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48208 — 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-48208 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