CVE-2009-4699 json
Multiple cross-site scripting (XSS) vulnerabilities in SkaDate Dating allow remote attackers to inject arbitrary web script or HTML via the…
published 16y ago modified 4mo ago also EUVD-2009-4663
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- public exploits
- 1
- Exploit-DB
Summary
Multiple cross-site scripting (XSS) vulnerabilities in SkaDate Dating allow remote attackers to inject arbitrary web script or HTML via the PATH_INFO to (1) admin/auth.php and (2) file_uploader.php.
Is CVE-2009-4699 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-9260)
- Published
Exploit prediction
3.37% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-9260 skadate dating - Local File Inclusion / Remote File Inclusion / Cross-Site Scripting webapps, 2009-07-27
- osvdb.org http://osvdb.org/56545 referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://osvdb.org/56544 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/35813 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
exploit-db.com
/exploits/9260
exploit
-
osvdb.org
/56545
vdb-entry, exploit
-
osvdb.org
/56544
vdb-entry, exploit
-
securityfocus.com
/bid/35813
vdb-entry, exploit
-
secunia.com
/advisories/35997
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/52004
vdb-entry
Sources
- CVE List CVE-2009-4699
- NVD CVE-2009-4699
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.