dbcve.org
Prtg Network MonitorApplication · Paessler

CVE-2025-67833

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-14
Fix available
A fix is available. Upgrade to 25.4.114.1032 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Paessler PRTG Network Monitor before 25.4.114 allows XSS by an unauthenticated attacker via the tag parameter.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Paessler PRTG Network Monitor versions prior to 25.4.114. An unauthenticated attacker can inject malicious JavaScript code through the tag parameter, which gets stored and executed when other users view affected content.

MitigationUpgrade PRTG Network Monitor to version 25.4.114 or later. As an interim measure, implement WAF rules or input validation to sanitize the tag parameter before full patching.

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:< 25.4.114.1032

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 installed PRTG version
    Log into the PRTG web interface and navigate to Setup > System Administration > System Status, or check the PRTG Administration Tool on the server. The version number is displayed clearly.
    Affected if The installed version is earlier than 25.4.114.1032 (e.g., 25.3.x, 24.x.x, or earlier)
  2. Identify PRTG web interface exposure
    Determine if the PRTG web interface is accessible externally or on network segments accessible to untrusted users. Check firewall rules and reverse proxy configurations for ports used by PRTG (default TCP 443).
    Affected if The PRTG web interface is reachable by unauthenticated or untrusted users on the network or internet
  3. Review HTTP access logs for tag parameter abuse
    Examine PRTG web server logs (located in the PRTG installation directory under /logs or /Log) for unusual requests targeting endpoints that accept the 'tag' parameter. Look for patterns containing script tags in tag parameter values.
    Affected if Log entries show requests with malicious JavaScript or HTML in tag parameter values (e.g., <script>, javascript:, onerror=)
  4. Check for stored suspicious content in PRTG objects
    Navigate to the device or group list in PRTG and review the Tags field for any unexpected entries containing script tags, event handlers, or encoded payloads. Use the search or filter functionality if available.
    Affected if Any device, group, or probe object has a tag containing JavaScript code or HTML tags that were not intentionally added by an administrator

You are affected if your PRTG version is earlier than 25.4.114.1032 and the web interface is accessible to unauthenticated users or attackers who can submit tag parameters.

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.114.1032 or later
Fixed in 25.4.114.1032
Interim mitigation

Upgrade PRTG Network Monitor to version 25.4.114 or later. As an interim measure, implement WAF rules or input validation to sanitize the tag parameter before full patching.

Recommended fix High confidence

25.4.114.1032

  1. Verify current PRTG Network Monitor version in the web interface under Setup > System Administration > Server Settings > Product Version
  2. Download PRTG Network Monitor version 25.4.114.1032 or later from the official Paessler download center at paessler.com/download
  3. Back up the PRTG configuration database (auto-created by installer, but manual backup recommended)
  4. Stop the PRTG Core Service before upgrading if prompted by the installer
  5. Run the PRTG installer and follow the upgrade wizard prompts
  6. After installation, verify the new version number matches 25.4.114.1032 or higher
  7. Clear browser cache and test that the tag parameter input is properly sanitized

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

Fix this in Prtg Network Monitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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