CVE-2026-30812
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 · uneditedImproper Neutralization of Input During Web Page Generation vulnerability allows Stored Cross-Site Scripting via event comments. This issue affects Pandora FMS: from 777 through 800
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Pandora FMS where event comments are not properly sanitized before being rendered in web pages. User-supplied input in comments is stored and executed when other users view the event, allowing attackers to inject malicious JavaScript code that executes in the victim's browser.
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>= 777, < 800.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Pandora FMS versionAccess the Pandora FMS web console and navigate to 'Setup' > 'About' or check the version via the API endpoint /pandora_console/include/api.php?op=get&op2=version. Alternatively, check the version file in the installation directory if you have server access.Affected if The version is 777 or higher but lower than 800.1
-
Confirm event viewer is accessibleLog into the Pandora FMS web interface and navigate to 'Events' > 'View Events'. Verify that the event viewer module loads successfully.Affected if The event viewer interface is accessible and displays events
-
Check if event comments can be viewedOpen any event in the event viewer by clicking on it. Locate the 'Comments' or 'Notes' section within the event detail view.Affected if Event comments are displayed in the web interface and can be viewed by users
Your environment is affected if you are running Pandora FMS version 777 through 800.0.x and the event comments feature is accessible in the web interface.
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 · scoped800.1
Implement proper server-side input validation and output encoding for event comments. Use context-appropriate HTML encoding functions when rendering user-supplied content in HTML pages, and consider implementing Content Security Policy (CSP) headers as defense-in-depth.
800.1 or later stable release
- 1. Back up the current Pandora FMS database and configuration files before starting the upgrade process
- 2. Review the official Pandora FMS upgrade documentation at pandorafms.com for your specific deployment method
- 3. Download Pandora FMS version 800.1 or later from the official source
- 4. Stop the Pandora FMS services (pandora_server and tendaemon)
- 5. Execute the upgrade following the documented upgrade procedure for your installation type
- 6. Verify the upgrade was successful by checking the version in the web interface
- 7. Test that event comments can be created and displayed without triggering XSS vulnerabilities
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30812 — 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-2026-30812 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