CVE-2009-4791 json
Multiple SQL injection vulnerabilities in Family Connections (aka FCMS) before 1.8.2 allow remote attackers to execute arbitrary SQL comman…
published 16y ago modified 4mo ago also EUVD-2009-4754
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Family Connections (aka FCMS) before 1.8.2 allow remote attackers to execute arbitrary SQL commands via the (1) letter parameter to addressbook.php, (2) id parameter to recipes.php, (3) year parameter to register.php, (4) poll_id parameter to home.php, and (5) email parameter to lostpw.php.
Patch / fix
Is CVE-2009-4791 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-8319)
- Published
Exploit prediction
1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-8319 family connection 1.8.1 - Multiple Vulnerabilities webapps, 2009-03-30
- securityfocus.com http://www.securityfocus.com/bid/34297 referenced PoC, tagged "exploit" by a source, unverified
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-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
securityfocus.com
/bid/34297
vdb-entry, exploit, patch
-
exploit-db.com
/exploits/8319
exploit
-
secunia.com
/advisories/34503
third-party-advisory, vendor-advisory
- familycms.com /blog/2009/03/fcms-182-released/
-
securityfocus.com
/archive/1/502272/100/0/threaded
mailing-list
- sourceforge.net /project/shownotes.php?release_id=672266
- sourceforge.net /tracker/?func=detail&aid=2722736&group_id=189733&atid=930513
Sources
- CVE List CVE-2009-4791
- NVD CVE-2009-4791
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.