CVE-2023-41788
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Pandora FMS on all allows Accessing Functionality Not Properly Constrained by ACLs. This vulnerability allows attackers to execute code via PHP file uploads. 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 confidenceUnrestricted file upload vulnerability in Pandora FMS versions 700-773 allows authenticated attackers to upload dangerous PHP files and execute arbitrary code. Additionally, access control checks are not properly enforced, enabling functionality access beyond what ACLs should permit.
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, < 774CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed Pandora FMS versionAccess the Pandora FMS console or check the version file (typically via /pandora_console/about or admin panel)Affected if Version is 700 or higher but below 774
-
Verify file upload functionality is accessibleLog in as an authenticated user and navigate to file upload sections (e.g., file manager, document upload, or agent configuration)Affected if Authenticated users can access any file upload interface
-
Inspect upload directories for suspicious filesCheck common upload directories (typically under /pandora_console/images, /uploads, or /var/www/html/pandora_console/assets) for unexpected .php filesAffected if Any .php files exist in upload directories that were not explicitly authorized
-
Test for unrestricted PHP file uploadAttempt to upload a test file with .php extension through the file upload feature (if authorized testing is permitted in your environment)Affected if The system accepts and stores .php file extensions without validation blocking them
-
Review user ACL enforcementCheck if low-privilege users can access administrative functions (e.g., manage users, system configuration, plugin management) beyond their assigned roleAffected if Users can access functionality that their ACL role should not permit
Your environment is affected if the Pandora FMS version is 700 through 773 and either unauthenticated or low-privilege authenticated users can upload PHP files or access restricted administrative functions.
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 · scoped774
Implement strict file type validation (both extension and MIME type) to block PHP file uploads, and ensure all sensitive functionality is properly gated by ACL checks.
774
- Backup the current Pandora FMS installation and database before proceeding with the upgrade.
- Download Pandora FMS version 774 from the official Pandora FMS website (pandorafms.com).
- Follow the official Pandora FMS upgrade documentation to install version 774, ensuring all system requirements are met.
- After upgrade, verify that file upload functionality is properly restricted and PHP files cannot be uploaded as executable content.
- Confirm the vulnerability is resolved by attempting to upload a file with dangerous extensions (should be blocked in version 774).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41788 — 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-41788 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