CVE-2021-46677
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 · uneditedA XSS vulnerability exist in Pandora FMS version 756 and below, that allows an attacker to perform javascript code executions via the event filter name field.
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 confidenceA stored cross-site scripting (XSS) vulnerability in Pandora FMS version 756 and below allows attackers to inject malicious JavaScript code through the event filter name field, which gets executed when the field is rendered in the application.
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< 757CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Pandora FMS versionAccess the Pandora FMS console and navigate to 'Home' > 'About' or check the footer of any page for the version number. Alternatively, check the file /var/www/html/pandora_console/CHANGELOG.md or look for a version file in the installation directory.Affected if The displayed version is 756 or below, indicating the installation is within the affected range (< 757).
-
Verify event filter functionality accessLog into Pandora FMS with an administrator or operator account and navigate to 'Events' > 'Event filters' or 'Manage Events' > 'Filters' in the main menu to confirm the event filter feature is accessible.Affected if The event filter management interface is available and the user has permissions to create or edit event filters.
-
Inspect event filter names for suspicious contentAccess the event filters list as described above. Review each filter's name field for any unusual characters, HTML tags, or JavaScript code (such as <script>, javascript:, onload, onerror, or encoded payloads). Alternatively, query the database table tevent_filter for the name field: SELECT name FROM tevent_filter WHERE name LIKE '%<%' OR name LIKE '%javascript%' OR name LIKE '%on%=';Affected if Any event filter name contains HTML tags, JavaScript code, or suspicious patterns that could indicate stored XSS payload injection.
A user is affected if their Pandora FMS installation is version 756 or below AND they have event filters with malicious JavaScript payloads stored in the filter name field that would execute upon rendering.
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 · scoped757
Implement proper input validation and output encoding/sanitization on the event filter name field to neutralize malicious script payloads.
Version 757 or later
- Upgrade Pandora FMS to version 757 or later to resolve the XSS vulnerability in the event filter name field
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46677 — 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-2021-46677 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