CVE-2021-46676
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 transactional maps 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 confidenceAn XSS vulnerability in Pandora FMS version 756 and below allows attackers to inject and execute arbitrary JavaScript code through the transactional maps name field by inserting malicious scripts that are rendered when other users view the affected field.
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 installed Pandora FMS versionAccess the Pandora FMS console and navigate to Administration > Setup > About, or check the version file in the installation directory (typically includes a version.php or similar file). Alternatively, check the footer of any Pandora FMS page for the version number.Affected if The installed version is 756 or below, or any version prior to 757.
-
Verify transactional maps feature is enabledCheck if the transactional maps module is active in the Pandora FMS installation. Navigate to Views > Maps or look for transactional map creation options in the console. This is typically found under the Maps or Visualization section of the web interface.Affected if Transactional maps feature is enabled and accessible to users who can create or edit maps.
-
Inspect transactional map name field for stored contentAccess the database or Pandora FMS interface to view existing transactional maps. Check the map name field in the database table (commonly named tmap or similar, containing name fields) for any stored JavaScript tags, script elements, or HTML event attributes.Affected if The name field contains unescaped HTML/JavaScript content such as <script> tags, javascript: URIs, or event handlers like onload/onerror.
-
Review input validation on map name submissionCreate a test transactional map with a name containing a benign test string like <img src=x onerror=alert(1)> and observe if it is rendered as-is when the map is displayed. Intercept the HTTP request to see if any sanitization occurs server-side.Affected if The test script payload is rendered literally in the browser without encoding or sanitization, indicating the vulnerability is present.
A user is affected if their Pandora FMS installation is version 756 or below AND the transactional maps feature is in use, allowing unauthenticated or low-privilege users to inject malicious scripts into map names that execute when viewed by other users.
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 on the transactional maps name field to sanitize user-supplied input before rendering, preventing script injection.
Version 757 or later
- Upgrade Pandora FMS to version 757 or later to address the XSS vulnerability in the transactional maps name field.
- After upgrading, verify that the transactional maps functionality works correctly.
- Review release notes for version 757 for any security-related changes relevant to your deployment.
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-2021-46676 — 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-46676 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