CVE-2023-41793
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: Path Traversal vulnerability in Pandora FMS on all allows Path Traversal. This vulnerability allowed changing directories and creating files and downloading them outside the allowed directories. This issue affects Pandora FMS: from 700 through <776.
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 path traversal vulnerability in Pandora FMS allows authenticated attackers to use directory traversal sequences (e.g., ../) in file operation parameters to escape the intended directory constraints. This enables unauthorized file creation, modification, and download outside the designated allowed directories.
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, < 776CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 web interface and navigate to Administration > Setup > About, or check the version file in the installation directory if accessible via CLIAffected if The displayed version is greater than or equal to 700 AND less than 776
-
Verify authentication mechanism is enabledConfirm that user authentication is configured and functional on the Pandora FMS instanceAffected if The system allows authenticated user accounts to log in, as this CVE requires an authenticated attacker
-
Confirm file operation functionality existsLocate features that perform file operations such as file upload, download, or creation within the web interface, typically found in file management, backup, or reporting modulesAffected if File operation features are accessible to authenticated users without additional hardening
-
Check for directory traversal protectionReview any available security settings, WAF configurations, or input validation mechanisms that may filter or block '../' sequences in file path parametersAffected if No explicit path traversal protection is implemented on file operation endpoints
You are affected if your Pandora FMS version is 700 or higher but below 776, authenticated users exist, and file operation features are accessible to them without path traversal safeguards.
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 · scoped776
Upgrade to Pandora FMS version 776 or later which contains the security patch, or implement strict input validation that canonicalizes file paths and rejects traversal sequences before file operations.
776 or later
- Backup your current Pandora FMS installation and database before upgrading
- Download Pandora FMS version 776 or later from the official Pandora FMS repository or website
- Stop the Pandora FMS services (pandora_server and tentacle_server)
- Upgrade Pandora FMS to version 776 following the official upgrade documentation for your installation method
- Verify the upgrade was successful by checking the version number in the console
- Restart the Pandora FMS services
- Test that the path traversal vulnerability is fixed by attempting to access files outside the designated directories
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-2023-41793 — 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-41793 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