CVE-2022-26310
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 · uneditedPandora FMS v7.0NG.760 and below allows an improper authorization in User Management where any authenticated user with access to the User Management module could create, modify or delete any user with full admin privilege. The impact could lead to a vertical privilege escalation to access the privileges of a higher-level user or typically an admin user.
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 v7.0NG.760 and below contains an improper authorization vulnerability in the User Management module. Any authenticated user with access to this module can create, modify, or delete users with full administrator privileges, enabling vertical privilege escalation.
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<= 7.0_ng_760CVSS 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.
-
Identify installed Pandora FMS versionAccess the Pandora FMS console and navigate to Setup > About, or check the version file in the installation directory if accessible via CLI. Compare the version number to the affected range.Affected if The installed version is 7.0NG.760 or lower (any version <= 7.0_ng_760).
-
Verify User Management module access controlsLog in as a non-administrator user and attempt to access the User Management section (typically found under Administration > Users). Observe whether access is granted without proper authorization checks.Affected if Non-administrator authenticated users can access the User Management module.
-
Review user accounts for unauthorized administratorsAs an administrator, navigate to Administration > Users and examine the list of all user accounts. Check for admin-level accounts that were not created by known trusted administrators.Affected if There are administrator accounts that were not created by authorized administrators, or there are more admin users than expected.
-
Examine audit logs for user management operationsAccess the System Audit or Logs section in Pandora FMS and filter for events related to user creation, modification, or deletion. Look for operations performed by non-administrator accounts.Affected if Audit logs show user management operations performed by accounts that should not have elevated privileges.
A user is affected if their Pandora FMS installation is version 7.0NG.760 or lower AND non-administrator users can access the User Management module or unauthorized admin accounts exist in the system.
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 dataUpgrade to v7.0NG.760 FIXED754 or later. Until patched, restrict User Management module access to only trusted administrators and enable comprehensive audit logging on all user management operations.
- 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-2022-26310 — 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-26310 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