CVE-2025-67834
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 · uneditedPaessler PRTG Network Monitor before 25.4.114 allows XSS by an unauthenticated attacker via the filter 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 confidenceAn unauthenticated cross-site scripting (XSS) vulnerability in Paessler PRTG Network Monitor allows remote attackers to inject arbitrary JavaScript code through the filter parameter in versions prior to 25.4.114.
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< 25.4.114.1032CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if PRTG Network Monitor is installedCheck for PRTG services in Windows Services, or scan for PRTG web server on common ports (80, 443, 8080, 8443)Affected if PRTG Network Monitor service is found or web interface is accessible on expected ports
-
Determine installed PRTG versionAccess PRTG web interface and navigate to Setup > System Administration > System Status to view version, or check version file in installation directory (C:\Program Files (x86)\PRTG Network Monitor\PRTG Server Manager.exe or similar)Affected if Version number cannot be determined or PRTG is not accessible
-
Compare version against affected rangeCompare the detected version number to the affected range: versions prior to 25.4.114.1032 are vulnerable. The full version format is typically 25.4.114.xxxx where xxxx is the build numberAffected if Version is below 25.4.114.1032 (for example, 25.4.113.9812 or earlier)
-
Verify web interface accessibilityConfirm the PRTG web interface is reachable without authentication on the network. The XSS in the filter parameter is exploitable by unauthenticated remote attackersAffected if PRTG is running a vulnerable version AND the web interface is network-accessible
A user is affected if PRTG Network Monitor is installed and the detected version is below 25.4.114.1032 with the web interface accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped25.4.114.1032
Upgrade PRTG Network Monitor to version 25.4.114 or later to remediate this XSS vulnerability.
25.4.114.1032 or later
- Back up your current PRTG configuration and database before upgrading
- Download PRTG Network Monitor version 25.4.114.1032 or later from the official Paessler download page (paessler.com)
- Stop the PRTG Core Service and all PRTG Probe services
- Run the installer with administrator privileges
- Follow the on-screen installation wizard to complete the upgrade
- Restart the PRTG services after installation completes
- Verify the upgrade by checking the PRTG version in the web interface under Setup > System Administration > System Status
- Test that the filter parameter is properly sanitized and no longer accepts malicious script content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67834 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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