CVE-2024-35306
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 · uneditedOS Command injection in Ajax PHP files via HTTP Request, allows to execute system commands by exploiting variables. This issue affects Pandora FMS: from 700 through <777.
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 confidenceOS Command Injection vulnerability in Pandora FMS Ajax PHP files allows remote attackers to execute arbitrary system commands via HTTP request variables. This affects versions 700 through <777 with a critical CVSS 9.8 rating.
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, < 777CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 if Pandora FMS is installedLook for the Pandora FMS web application directory, typically found at /var/www/html/pandora_console or similar web root paths. Check for the presence of the 'pandora' directory containing PHP files.Affected if The Pandora FMS web application directory exists on the server
-
Check the installed Pandora FMS versionLocate the version file or check the dashboard footer. Common locations include: /pandora_console/include/config.php (look for $config['version'] or similar), or log into the web interface and check Help > About. Compare the version number against the affected range.Affected if The installed version is 700 or higher but lower than 777
-
Verify the Ajax PHP interface is accessibleTest network accessibility to the /pandora_console/ajax.php endpoint by attempting a request to it (e.g., curl -I https://target/pandora_console/ajax.php). The vulnerability exists in the Ajax PHP files.Affected if The /pandora_console/ajax.php endpoint responds and is reachable from the network
-
Check for public network exposureDetermine if the Pandora FMS web interface is exposed to the public internet or untrusted networks by reviewing firewall rules, reverse proxy configurations, or network ACLs.Affected if The Pandora FMS web interface is accessible from untrusted network segments or the public internet
You are affected if Pandora FMS is installed with version 700 or higher but below 777, and the Ajax PHP interface is network-accessible.
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 · scoped777
Upgrade Pandora FMS to version 777 or later. Until then, restrict network access to the PHP endpoints and implement web application firewall rules to detect/block malicious parameter patterns.
777
- Backup your current Pandora FMS installation and database before proceeding
- Download Pandora FMS version 777 or later from the official pandorafms.com downloads section
- Consult the official Pandora FMS upgrade documentation for your specific installation type
- Execute the upgrade following the documented upgrade procedure
- Verify the upgrade was successful by accessing the Pandora FMS web console
- Confirm that the Ajax functionality is operational after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35306 — 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-2024-35306 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