CVE-2010-4282 in the critical feed json
Multiple directory traversal vulnerabilities in Pandora FMS before 3.1.1 allow remote attackers to include and execute arbitrary local file…
published 2010-12-02 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4255
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 19.6%
- EPSS 19.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
Multiple directory traversal vulnerabilities in Pandora FMS before 3.1.1 allow remote attackers to include and execute arbitrary local files via (1) the page parameter to ajax.php or (2) the id parameter to general/pandora_help.php, and allow remote attackers to include and execute, create, modify, or delete arbitrary local files via (3) the layout parameter to operation/agentes/networkmap.php.
Patch / fix
Timeline
- First public exploit (EDB-15643)
- Published
Exploit prediction
19.65% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15643 Pandora Fms 3.1 - Directory Traversal / Local File Inclusion webapps, 2010-11-30
- Nuclei template Pandora Fms < 3.1.1 - Directory Traversal nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
sourceforge.net
/projects/pandora/files/Pandora%20FMS%203.1/Final%20version%20%28Stable%29/pandorafms_console-3.1_security_pat
patch
-
securityfocus.com
/bid/45112
vdb-entry, patch
-
exploit-db.com
/exploits/15643
exploit
-
osvdb.org
/69545
vdb-entry
-
secunia.com
/advisories/42347
third-party-advisory
-
securityfocus.com
/archive/1/514939/100/0/threaded
mailing-list
-
osvdb.org
/69543
vdb-entry
-
osvdb.org
/69544
vdb-entry
-
seclists.org
/fulldisclosure/2010/Nov/326
mailing-list
Sources
- CVE List CVE-2010-4282
- NVD CVE-2010-4282
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.