dbcve.org
Prtg Network MonitorApplication · Paessler

CVE-2023-31452

HIGH · 8.8 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 23.3.86.1520 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) token bypass was identified in PRTG 23.2.84.1566 and earlier versions that allows remote attackers to perform actions with the permissions of a victim user, provided the victim user has an active session and is induced to trigger the malicious request. This could force PRTG to execute different actions, such as creating new users. The severity of this vulnerability is high and received a score of 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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

CSRF token bypass in PRTG Network Monitor versions 23.2.84.1566 and earlier allows remote attackers to bypass anti-CSRF protections and perform authenticated actions (such as creating new users) by tricking authenticated users into triggering malicious requests.

MitigationUpdate PRTG Network Monitor to a version that addresses this vulnerability; until then, minimize exposure by restricting administrative access and user interaction with the web interface.

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
Prtg Network MonitorApplication
Affected:< 23.3.86.1520

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check PRTG Network Monitor version in web interface
    Log into the PRTG web interface, click the gear icon (setup) in the top right, and select 'About PRTG' from the System Administration section. Note the version number displayed.
    Affected if The displayed version is 23.2.84.1566 or earlier, or any version lower than 23.3.86.1520.
  2. Check PRTG version via Windows Programs and Features
    Open Windows Control Panel, go to Programs and Features, find 'PRTG Network Monitor' in the list, and note the version in the Version column.
    Affected if The listed version is 23.2.84.1566 or earlier, or any version lower than 23.3.86.1520.
  3. Check PRTG version via Administration Tool
    Open the PRTG Administration Tool (installed with PRTG), navigate to the 'About' or 'System Status' tab, and record the version number shown.
    Affected if The version shown is 23.2.84.1566 or earlier, or any version lower than 23.3.86.1520.
  4. Confirm CSRF protection is in use
    In the PRTG web interface, inspect the source code of any page or check the HTTP headers of requests for the presence of anti-CSRF tokens (often named '__CSRFTOKEN', 'csrf_token', or similar). Use browser developer tools (F12) to examine form submissions or request headers.
    Affected if Anti-CSRF tokens are present in the interface, but the installed version is vulnerable to bypass (version < 23.3.86.1520).

You are affected if your installed PRTG Network Monitor version is any release earlier than 23.3.86.1520, as the anti-CSRF protection in those versions can be bypassed.

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

Update PRTG Network Monitor to a version that addresses this vulnerability; until then, minimize exposure by restricting administrative access and user interaction with the web interface.

Recommended fix High confidence

23.3.86.1520 or later

  1. Backup the current PRTG configuration before proceeding with the upgrade
  2. Download PRTG Network Monitor version 23.3.86.1520 or later from the official Paessler website (www.paessler.com)
  3. Install or upgrade to PRTG Network Monitor version 23.3.86.1520 or later
  4. Verify the installation was successful and the web interface is accessible
  5. Log in and confirm the CSRF protection is functioning correctly in the updated version
Caveat Standard upgrade caution applies - test in non-production environment first

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

Fix this in Prtg Network Monitor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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