CVE-2021-46678
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 service 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 · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability in Pandora FMS versions 756 and below allows attackers to inject malicious JavaScript code through the service name field. When other users view or interact with the affected service, the injected script executes in their browser context, potentially stealing session cookies or performing actions on behalf of the victim.
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 installation and versionLocate the Pandora FMS installation and determine the installed version number. This is typically visible in the product UI footer, or can be found in version files within the installation directory. Compare your version against the affected range: versions 756 and below are vulnerable.Affected if The installed version is 756 or lower (less than 757).
-
Verify access to service management featuresLog into the Pandora FMS console and navigate to the service management or configuration section where service objects can be created or edited. Confirm that the service name input field is present and accessible.Affected if You have access to create or edit services and can view the service name field.
-
Inspect existing service configurations for injected contentReview all configured services in the system. Examine the service name field for each service entry. Look for any unexpected characters, script tags, or HTML markup within the name values that were not intentionally entered.Affected if Any service name contains JavaScript tags, HTML elements, or suspicious encoded characters that were not purposefully configured.
Your environment is affected if you are running Pandora FMS version 756 or below and have access to service management where a malicious service name could be stored or already exists in the configuration.
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
Update Pandora FMS to a version newer than 756. If immediate patching is not feasible, implement proper input validation and output encoding on all service name fields and ensure Content Security Policy headers are configured to mitigate XSS.
Pandora FMS version 757 or later
- 1. Backup your current Pandora FMS installation and database before upgrading
- 2. Download Pandora FMS version 757 or later from the official Pandora FMS repository or website
- 3. Follow the official upgrade documentation for your specific installation type (standalone, cluster, or container)
- 4. Verify the service name field now properly sanitizes input to prevent XSS execution
- 5. Test the upgrade in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46678 — 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-46678 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