CVE-2010-1934 json
Multiple PHP remote file inclusion vulnerabilities in openMairie openPlanning 1.00, when register_globals is enabled, allow remote attacker…
published 16y ago modified 4mo ago also EUVD-2010-1953
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
Multiple PHP remote file inclusion vulnerabilities in openMairie openPlanning 1.00, when register_globals is enabled, allow remote attackers to execute arbitrary PHP code via a URL in the path_om parameter to (1) categorie.class.php, (2) profil.class.php, (3) collectivite.class.php, (4) ressource.class.php, (5) droit.class.php, (6) utilisateur.class.php, and (7) planning.class.php in obj/.
Is CVE-2010-1934 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-12365)
- Published
Exploit prediction
2.90% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-12365 Openplanning 1.00 - Local File Inclusion / Remote File Inclusion webapps, 2010-04-24
- packetstormsecurity.org http://packetstormsecurity.org/1004-exploits/openplanning-rfilfi.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
exploit-db.com
/exploits/12365
exploit
-
packetstormsecurity.org
/1004-exploits/openplanning-rfilfi.txt
exploit
-
secunia.com
/advisories/39606
third-party-advisory, vendor-advisory
-
osvdb.org
/64191
vdb-entry
-
osvdb.org
/64187
vdb-entry
-
osvdb.org
/64186
vdb-entry
-
osvdb.org
/64188
vdb-entry
-
osvdb.org
/64192
vdb-entry
-
osvdb.org
/64189
vdb-entry
Sources
- CVE List CVE-2010-1934
- NVD CVE-2010-1934
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.