U.S. CISA adds Microsoft .NET Framework, Apache OFBiz, and Paessler PRTG Network Monitor flaws to its Known Exploited Vulnerabilities catalog

CVE-2018-19410 is a local file inclusion (LFI) flaw in the PRTG Network Monitor web login page (/public/login.htm) where an attacker can override the 'include' directive via a crafted HTTP request. By directing the include to /api/addusers and supplying the 'id' and 'users' parameters, a remote, unauthenticated attacker triggers that API and creates a new user with read-write privileges, including full administrator. Effectively, this gives an unauthenticated remote attacker persistent, privileged access to the monitoring server's console, with visibility into monitored infrastructure and the ability to alter monitoring configuration. Any PRTG Network Monitor deployment running a version prior to 18.2.40.1683 is affected, with risk concentrated on instances whose web interface is reachable by attackers (internet-exposed consoles, or consoles reachable from compromised internal networks). The flaw is being actively exploited: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-02-04 with a federal patch deadline of 2025-02-25, and its EPSS score of 97.9% (100th percentile) indicates near-certain likelihood of exploitation within 30 days, though no public proof-of-concept is known.

Do: Upgrade PRTG Network Monitor to version 18.2.40.1683 or later (current releases include the fix; CISA's required action is to apply vendor mitigations or discontinue use). Until patched, restrict access to the PRTG web console (e.g., firewall it to trusted management networks and avoid internet exposure). Review the web server logs for unauthenticated requests to /public/login.htm with manipulated 'include' parameters or calls to /api/addusers, and audit existing PRTG user accounts for unauthorized administrator accounts created via this flaw.

Paessler PRTG Network Monitor versions before 18.2.39 contain an OS command injection flaw (CWE-78) in the PRTG System Administrator web console. An attacker with administrative access to that console can trigger arbitrary command execution on both the PRTG server and on monitored devices by sending malformed parameters in sensor or notification management scenarios, with high impact on confidentiality, integrity, and availability (CVSS 3.1: 7.2, high privileges required, no user interaction). Any organization running PRTG Network Monitor older than 18.2.39 is affected, although exploitation requires valid administrative access to the console. CISA added the flaw to the Known Exploited Vulnerabilities catalog on 2025-02-04, confirming active in-the-wild exploitation, with public proof-of-concept references (Exploit-DB 46527 and two PacketStorm entries) and an EPSS probability of 87% of exploitation within 30 days. Defenders running unpatched PRTG instances, especially consoles reachable from the internet, should treat this as actively targeted.

Do: Upgrade PRTG Network Monitor to 18.2.39 or later (any current release includes the fix); per CISA's KEV entry, apply vendor mitigations or discontinue use of unpatched versions by the February 25, 2025 deadline. Inventory PRTG servers — particularly consoles exposed to the internet — restrict System Administrator console access to trusted users and networks, and audit sensor and notification configurations and logs for tampering or unexpected command execution.

CVE-2024-29059 is an information disclosure flaw in Microsoft .NET Framework (CWE-209), in which error handling can generate error messages containing sensitive information. Per the CVSS vector, it is exploitable over the network by an unauthenticated attacker with no user interaction, with high impact to confidentiality only. An attacker who can reach an affected application can trigger the flaw and harvest sensitive details from error output, which can support further attacks against the host or its users. Any organization running affected .NET Framework versions, most commonly on Windows servers hosting ASP.NET/.NET web workloads, is in scope. The vulnerability is being actively exploited: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-02-04 with a remediation deadline of 2025-02-25, EPSS puts the 30-day exploitation probability at 98.6%, and no public proof-of-concept is known while ransomware use is unconfirmed.

Do: Apply Microsoft's current monthly security updates for affected .NET Framework versions as soon as possible, ahead of CISA's February 25, 2025 KEV deadline. Inventory Windows hosts and prioritize internet-facing servers and systems running ASP.NET/.NET Framework applications, confirming installed .NET Framework versions against Microsoft's advisory. If patching must be delayed, follow vendor-recommended mitigations or restrict network access to affected applications until updates are applied.

Apache OFBiz, the open-source ERP and e-commerce framework from the Apache Software Foundation, is affected by a forced browsing vulnerability (CWE-425), meaning the application fails to properly verify a requester's authorization for certain restricted resources. A remote attacker triggers the flaw by directly requesting protected URLs or endpoints (navigating straight to them rather than through the intended application flow), thereby bypassing access-control checks. Successful exploitation grants the attacker unauthorized access to the affected OFBiz instance, as described by CISA; the available data does not detail what specific functionality or data is exposed. Any organization running Apache OFBiz, particularly internet-facing deployments, is affected, though no specific version range is listed in the available data. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2025-02-04, indicating confirmed exploitation in the wild, and EPSS assigns it an approximately 100% probability of exploitation within 30 days (top percentile); no public proof-of-concept is known.

Do: Apply the mitigations specified in CISA's required action and per Apache's advisory, or discontinue use of the product if mitigations are unavailable; upgrade to the fixed OFBiz release identified in the vendor advisory. Check OFBiz access logs for direct, unauthenticated requests to restricted URLs, especially around and after the 2025-02-04 KEV listing, and restrict internet exposure of OFBiz front-ends and administrative screens.