Security readout for executives and security teams
Plain-English summary
This flaw lets a low-privileged, read-only PRTG Network Monitor user create a higher-privileged account, potentially including an administrator. The attacker already needs authenticated access, but the impact can be full administrative control of the monitoring system. Monitoring platforms often hold sensitive infrastructure visibility, so affected deployments should be treated seriously.
Executive priority
Prioritize remediation for internet-reachable or widely accessible PRTG deployments. The issue can turn a low-privilege account into administrative control, but evidence supplied here does not show active exploitation. Treat it as a high-impact authenticated privilege escalation.
Technical view
PRTG Network Monitor versions before 18.2.40.1683 had improper authorization checking on /api/addusers. A read-only authenticated user could create a read-write or administrator account because the API endpoint did not properly enforce user rights. No CVSS, CWE, or vendor affected-product metadata is included in the supplied bundle.
Likely exposure
Exposure is limited to organizations running PRTG Network Monitor before 18.2.40.1683 with accounts that can authenticate to the web/API interface. Risk increases where PRTG is reachable beyond trusted administration networks or where read-only accounts are broadly issued.
Exploitation context
The supplied sources do not show CISA KEV listing or active exploitation evidence. The described attack requires authenticated access and abuses authorization failure in the user-creation API. Public exploit status is not established by the provided bundle.
Researcher notes
The source bundle is sparse: no CVSS vector, CWE mapping, CPE list, or detailed vendor advisory text is included. Analysis is grounded in the CVE description and PT Security reference only. Avoid assuming unauthenticated access, specific exploit availability, or broader Paessler product impact.
Mitigation direction
- Upgrade affected PRTG Network Monitor instances to 18.2.40.1683 or a later supported release.
- Check Paessler or vendor guidance for current patch and hardening recommendations.
- Restrict PRTG web and API access to trusted administrative networks.
- Review read-only accounts and remove unnecessary access.
- Audit for unexpected administrator or read-write accounts.
Validation and detection
- Inventory all PRTG Network Monitor versions in use.
- Flag any instance older than 18.2.40.1683 as affected.
- Review user creation history for unexpected privileged accounts.
- Check logs for suspicious /api/addusers activity where available.
- Confirm read-only accounts cannot create users after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-19411 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ptsecurity.com/ww-en/analytics/threatscape/pt-2018-25/CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.