CVE-2023-41792
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Pandora FMS on all allows Cross-Site Scripting (XSS). This vulnerability allowed Javascript code to be executed in the SNMP Trap Editor. This issue affects Pandora FMS: from 700 through 773.
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 CSRF vulnerability in Pandora FMS allows attackers to inject malicious JavaScript code into the SNMP Trap Editor. The lack of anti-CSRF tokens on state-changing forms in this component enables attackers to craft requests that persist XSS payloads, which execute when legitimate users access the trap editor.
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>= 700, <= 773CVSS 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 the installed Pandora FMS versionLocate and read the version file or access the admin UI to view the system version information. Common locations include /var/www/html/pandora_console/include/config.php or the 'About' section in the web interface.Affected if The installed version falls within the range 700 through 773 inclusive.
-
Verify SNMP Trap Editor is accessibleLog into Pandora FMS as an administrator and navigate to the SNMP Trap Editor section (typically under 'SNMP' > 'Trap Editor' or similar). Confirm the module loads and is usable.Affected if The SNMP Trap Editor module is present and accessible to users.
-
Inspect SNMP Trap Editor forms for CSRF protectionUse browser developer tools to view the HTML source of state-changing forms in the SNMP Trap Editor (such as forms that create, modify, or delete trap entries). Look for hidden input fields containing anti-CSRF tokens or similar security tokens.Affected if The forms do not contain anti-CSRF tokens or any token-based protection mechanism.
-
Test for stored XSS via SNMP Trap EditorCreate or modify a trap entry using the SNMP Trap Editor with a test XSS payload (such as <script>alert(1)</script>) in a trap field. Save the entry, then access the trap editor again to see if the payload executes or is rendered unescaped.Affected if The submitted payload is stored and rendered without proper output encoding when the trap editor is accessed.
A user is affected if their Pandora FMS version is between 700 and 773 inclusive, the SNMP Trap Editor is accessible, and the forms lack CSRF token protection allowing XSS payload injection.
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.
From vendor dataApply vendor patches for CVE-2023-41792. If no patch is available, implement CSRF token validation on all SNMP Trap Editor forms and enforce strict input validation with output encoding for any user-supplied data rendered in the editor.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41792 — 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-2023-41792 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