dbcve.org
NetalertxApplication

CVE-2025-32440

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to 25.4.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
NetAlertX is a network, presence scanner and alert framework. Prior to version 25.4.14, it is possible to bypass the authentication mechanism of NetAlertX to update settings without authentication. An attacker can trigger sensitive functions within util.php by sending crafted requests to /index.php. This issue has been patched in version 25.4.14.

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

NetAlertX versions prior to 25.4.14 contain an authentication bypass vulnerability that allows unauthenticated attackers to update application settings by sending crafted requests to /index.php that invoke sensitive functions in util.php. This enables full compromise of the application's configuration without valid credentials.

MitigationUpgrade NetAlertX to version 25.4.14 or later to remediate the authentication bypass. If immediate patching is not possible, restrict network access to /index.php from untrusted sources as a temporary mitigation.

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
NetalertxApplication
Affected:< 25.4.14

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

CVSS:3.1/AV:N/AC:L/PR:N/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 NetAlertX version
    Check the installed version of NetAlertX (typically found in the application admin panel, about page, or in version files within the installation directory)
    Affected if The installed version is less than 25.4.14 (the affected version range is < 25.4.14)
  2. Verify web interface accessibility
    Determine if the NetAlertX web interface is exposed to network access (check firewall rules, reverse proxy configuration, or direct exposure of port 80/443)
    Affected if The web interface is accessible from untrusted networks - this is required for the vulnerability to be exploitable by remote attackers
  3. Inspect application settings for unauthorized changes
    Review current application settings in the NetAlertX admin panel or configuration files for any unexpected modifications (such as altered notification settings, new device entries, or changed scan parameters)
    Affected if Settings have been modified that were not made by legitimate administrators, indicating potential exploitation
  4. Check access logs for suspicious requests
    Examine web server access logs for requests to /index.php that lack valid authentication tokens or session cookies, particularly those modifying configuration parameters
    Affected if There are unauthenticated requests to /index.php with parameter modifications that succeeded

A user is affected if their NetAlertX installation is version < 25.4.14 AND the web interface is accessible to potential attackers (untrusted networks).

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 25.4.14 or later
Fixed in 25.4.14
Interim mitigation

Upgrade NetAlertX to version 25.4.14 or later to remediate the authentication bypass. If immediate patching is not possible, restrict network access to /index.php from untrusted sources as a temporary mitigation.

Recommended fix High confidence

NetAlertX version 25.4.14

  1. 1. Back up the current NetAlertX installation and database before proceeding with the upgrade.
  2. 2. Upgrade NetAlertX to version 25.4.14 or later (e.g., download from the official GitHub repository).
  3. 3. Restart the NetAlertX service to ensure the patched code is loaded.
  4. 4. Verify the authentication bypass is fixed by attempting to access /index.php without credentials and confirming authentication is required.
  5. 5. Verify all existing functionality works correctly after the upgrade.

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

Fix this in Netalertx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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