CVE-2023-41786
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Pandora FMS on all allows File Discovery. This vulnerability allows users with low privileges to download database backups. This issue affects Pandora FMS: from 700 through 772.
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 confidencePandora FMS contains an access control flaw in its File Discovery feature that allows authenticated users with low privileges to bypass authorization checks and download sensitive database backup files. The vulnerability stems from improper validation of user permissions when accessing the file download functionality, exposing critical data including full database contents and potentially credentials.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 admin console and navigate to the 'About' or 'System Information' section, or query the system via command line if available (e.g., 'pandora_fms --version' or check installation logs). Compare the version number against the affected range: versions 700 through 772 are vulnerable.Affected if The installed version is 700 or higher but lower than 773.
-
Confirm File Discovery module is activeLog into the Pandora FMS web interface as a standard (low-privilege) user. Navigate to the File Discovery section under the appropriate menu tree (typically under 'Operations' or 'Discovery' depending on version). Check if the module is visible and accessible in the user interface.Affected if The File Discovery feature is present and accessible to the user account.
-
Verify file download permissionsAs a low-privilege authenticated user, attempt to access the File Discovery download functionality. Check if the interface allows navigation to database backup files or if authorization prompts appear when attempting to access files outside intended scope.Affected if Low-privilege users can download database backup files without proper authorization errors.
-
Locate database backup filesReview the Pandora FMS configuration and backup storage settings. Identify the directory where database backups are stored (commonly a 'backup' or 'dump' directory within the Pandora FMS data folder). Verify if this directory is within the web server's document root.Affected if Database backup files are stored in a web-accessible directory accessible via HTTP/HTTPS.
A system is affected if it runs Pandora FMS version 700-772 with the File Discovery module enabled and accessible to low-privilege users, allowing unauthorized download of database backups.
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 · scoped773
Apply the vendor patch or upgrade to a version beyond 772 that addresses the improper access control in the File Discovery module. Additionally, restrict network access to administrative interfaces and verify that database backup files are stored outside web-accessible directories.
773
- Review current Pandora FMS installation and confirm exact version (700-772)
- Schedule maintenance window for upgrade procedure
- Backup current Pandora FMS database and configuration files
- Download Pandora FMS version 773 from official source
- Stop Pandora FMS services before upgrade
- Upgrade Pandora FMS to version 773 following official installation/upgrade documentation
- Verify upgrade completed successfully
- Restart Pandora FMS services
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41786 — 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-41786 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