CVE-2024-46506 in the critical feed json
NetAlertX 23.01.14 through 24.x before 24.10.12 allows unauthenticated command injection via settings update because function=savesettings…
published last yr. modified 4mo ago also EUVD-2025-14500
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 62.7%
- EPSS 62.7% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 1
- Metasploit
Summary
NetAlertX 23.01.14 through 24.x before 24.10.12 allows unauthenticated command injection via settings update because function=savesettings lacks an authentication requirement, as exploited in the wild in May 2025. This is related to settings.php and util.php.
Patch / fix
- NetAlertX NetAlertX 24.10.12
Is CVE-2024-46506 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/linux/http/netalertx_rce_cve_2024_46506)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
62.67% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- Metasploit exploit/linux/http/netalertx_rce_cve_2024_46506 Unauthenticated RCE in NetAlertX metasploit exploit, excellent rank, 2025-01-30
- rhinosecuritylabs.com https://rhinosecuritylabs.com/research/cve-2024-46506-rce-in-netalertx/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- NetAlertX NetAlertX
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
rhinosecuritylabs.com
/research/cve-2024-46506-rce-in-netalertx/
exploit, third-party-advisory
Sources
- CVE List CVE-2024-46506
- NVD CVE-2024-46506
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.