dbcve.org
Pandora FmsApplication · Pandorafms

CVE-2021-46679

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 757 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
A XSS vulnerability exist in Pandora FMS version 756 and below, that allows an attacker to perform javascript code executions via service elements.

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

A stored Cross-Site Scripting (XSS) vulnerability in Pandora FMS version 756 and below allows attackers to inject malicious JavaScript code through service elements, which is then executed when other users view the affected content.

MitigationUpgrade Pandora FMS to a version beyond 756 that includes the security patch. If immediate patching is not possible, implement input validation and output encoding on service element handling routines as a compensating control.

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
Pandora FmsApplication
Affected:< 757

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. Identify installed Pandora FMS version
    Access the Pandora FMS administration console and navigate to the 'About' or 'System Information' page, typically found under Admin > Setup or the main dashboard. Alternatively, check the version number displayed in the footer of the web interface or inspect the version file in the installation directory if you have filesystem access.
    Affected if The installed version is 756 or below (any version number less than 757).
  2. Confirm service elements feature is in use
    Navigate to the Service Management or Service Monitoring section within the Pandora FMS console. Look for any configured service elements such as service items, service templates, or service definitions that are actively monitoring infrastructure.
    Affected if Service elements are defined and visible within the console, indicating the feature is enabled and actively used.
  3. Inspect service element configurations for injected scripts
    Access each service element configuration and examine the fields used for defining service items, descriptions, and display labels. Review the raw configuration data stored in the database tables related to services (commonly tables prefixed with 'tservices' or 'tservice'), looking for script tags, event handlers, or javascript: URIs within text fields.
    Affected if Any service element configuration contains HTML script tags, javascript: protocols, or XSS payloads such as <script> tags, onerror= attributes, or similar malicious patterns in name, description, or display fields.

You are affected if your Pandora FMS installation is version 756 or below AND the service elements feature is actively used, as the XSS payload would be stored within service element configurations.

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 757 or later
Fixed in 757
Interim mitigation

Upgrade Pandora FMS to a version beyond 756 that includes the security patch. If immediate patching is not possible, implement input validation and output encoding on service element handling routines as a compensating control.

Recommended fix High confidence

Pandora FMS version 757 or higher

  1. 1. Backup your current Pandora FMS database and configuration files
  2. 2. Download Pandora FMS version 757 or later from the official source (pandorafms.com)
  3. 3. Stop the Pandora FMS services (tentacle_server, pandora_server)
  4. 4. Upgrade the Pandora FMS installation using the appropriate method for your deployment (standalone or OVA/ISO)
  5. 5. Verify the upgrade was successful by checking the version in the web interface
  6. 6. Test that the service elements functionality works properly after upgrade
  7. 7. Re-enable services and monitor for any issues

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

Fix this in Pandora Fms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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