CVE-2022-43980
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 · uneditedThere is a stored cross-site scripting vulnerability in Pandora FMS v765 in the network maps editing functionality. An attacker could modify a network map, including on purpose the name of an XSS payload. Once created, if a user with admin privileges clicks on the edited network maps, the XSS payload will be executed. The exploitation of this vulnerability could allow an atacker to steal the value of the admin user´s cookie.
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 exists in Pandora FMS v765 within the network maps editing functionality. Attackers can inject malicious JavaScript into network map names, which persists in the database. When an administrator views these network maps, the XSS payload executes, allowing attackers to steal admin session cookies.
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< 766CVSS 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 administration console and navigate to the system information or about page. Alternatively, check the version file in the Pandora FMS installation directory if you have file system access.Affected if The installed version is v765 or any version prior to v766 (e.g., v764, v763, etc.)
-
Verify network maps functionality accessLog into Pandora FMS as an administrator and check if you have access to the network maps module. Navigate to the network maps section (typically under 'Visualize' or 'Maps' in the main menu).Affected if The network maps feature is accessible and you can view or create network maps in the console
-
Inspect database for injected map namesQuery the Pandora FMS database (typically named pandora) for network map names. Look for suspicious patterns in the netflow_map or similar network map tables. Example SQL: SELECT name FROM tmap WHERE name LIKE '%<script%' OR name LIKE '%javascript:%' OR name LIKE '%onload=%';Affected if Any network map names contain HTML tags (script, iframe, object), JavaScript protocol handlers (javascript:), or event handlers (onload, onerror, onclick)
-
Check map rendering for XSS outputCreate a test network map with a benign test string containing special characters (e.g., <test>). View the map in the console and inspect the page source using browser developer tools to see if the characters are rendered as-is (vulnerable) or properly escaped.Affected if Special characters in network map names are rendered as raw HTML without escaping when viewed in the browser
You are affected if your Pandora FMS version is v765 or earlier AND you have network maps in your database with unsanitized names containing script tags or JavaScript event handlers that would execute when an administrator views those maps.
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 · scoped766
Implement proper input validation and output encoding on all network map name fields. Use context-aware escaping before rendering user-supplied data in HTML. Consider Content Security Policy headers to mitigate XSS impact.
Pandora FMS version 766 or later
- 1. Back up your current Pandora FMS installation and database before performing any upgrade.
- 2. Download Pandora FMS version 766 or later from the official Pandora FMS repository or website (pandorafms.com).
- 3. Follow the official upgrade documentation for your specific installation method (standalone, Docker, or appliance).
- 4. After upgrading, verify that the network maps functionality works correctly.
- 5. Test that the XSS vulnerability is no longer present by attempting to create a network map with a benign script payload in the name field.
- 6. Clear browser cookies and session data as a precaution after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43980 — 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-2022-43980 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