dbcve.org
HertzbeatApplication · Apache

CVE-2025-24404

HIGH · 8.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 1.7.0 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
XML Injection RCE by parse http sitemap xml response vulnerability in Apache HertzBeat. The attacker needs to have an authenticated account with access, and add monitor parsed by xml, returned special content can trigger the XML parsing vulnerability. This issue affects Apache HertzBeat (incubating): before 1.7.0. Users are recommended to upgrade to version 1.7.0, 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

This is an XML Injection vulnerability leading to Remote Code Execution (RCE) in Apache HertzBeat. An authenticated attacker with monitor access can add a monitor that fetches a specially crafted XML (sitemap) response. When HertzBeat parses this XML content, the XML parser processes external entities or other malicious XML constructs, allowing arbitrary code execution on the server.

MitigationUpgrade Apache HertzBeat to version 1.7.0 or later. This is the only reliable remediation as no workarounds are mentioned in the advisory.

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

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 if Apache HertzBeat is running
    Check running processes for 'hertzbeat' or look for the service listening on typical ports (8080, 1158). Use command: ps aux | grep -i hertzbeat or netstat -tlnp | grep -E '8080|1158'
    Affected if HertzBeat process is found running on the system
  2. Determine the installed HertzBeat version
    Check the HertzBeat startup banner, log files (usually in logs/ directory), or the about/page in the web UI. The version is often displayed in the banner on startup or in the log files under the installation directory
    Affected if Installed version is below 1.7.0 (e.g., 1.6.x, 1.5.x, etc.)
  3. Verify monitor feature is enabled and accessible
    Log into the HertzBeat web interface and navigate to the Monitors section. Check if the user has privileges to add or manage monitors. The vulnerability requires an authenticated user with monitor access
    Affected if Monitor functionality is available to authenticated users and monitors can be added or modified
  4. Check for URL/sitemap monitoring configuration
    In the HertzBeat web UI, go to Monitor -> Add Monitor. Look for monitor types that fetch external URLs or sitemaps (such as 'Website', 'API', or similar URL-based monitoring options)
    Affected if URL or sitemap-based monitoring types are available and can be configured by authenticated users

The environment is affected if Apache HertzBeat is running with a version lower than 1.7.0 and authenticated users have access to configure URL/sitemap monitors that trigger XML parsing.

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.0 or later
Fixed in 1.7.0
Interim mitigation

Upgrade Apache HertzBeat to version 1.7.0 or later. This is the only reliable remediation as no workarounds are mentioned in the advisory.

Recommended fix High confidence

1.7.0

  1. 1. Back up your current Hertzbeat configuration and data directory to prevent data loss during upgrade.
  2. 2. Download Apache Hertzbeat version 1.7.0 from the official Apache downloads page (https://hertzbeat.apache.org/download/).
  3. 3. Stop the running Hertzbeat service: systemctl stop hertzbeat (or the appropriate command for your setup).
  4. 4. Replace the existing Hertzbeat installation files with the new version 1.7.0 files.
  5. 5. Restore your backed-up configuration to the new installation.
  6. 6. Start the Hertzbeat service: systemctl start hertzbeat (or the appropriate command for your setup).
  7. 7. Verify the upgrade by logging into the web interface and confirming the version displays as 1.7.0.
  8. 8. Test that XML-based monitor functionality works correctly with the upgrade.

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

Fix this in Hertzbeat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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