CVE-2010-2684 json
SQL injection vulnerability in index.php in Customer Paradigm PageDirector CMS allows remote attackers to execute arbitrary SQL commands vi…
published 16y ago modified 4mo ago also EUVD-2010-2688
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in index.php in Customer Paradigm PageDirector CMS allows remote attackers to execute arbitrary SQL commands via the id parameter.
Is CVE-2010-2684 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-14089)
- Published
Exploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14089 PageDirector CMS - Multiple Vulnerabilities webapps, 2010-06-28
- securityfocus.com http://www.securityfocus.com/bid/41184 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1006-exploits/pagedirector-sqladdadmin.txt 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
-
exploit-db.com
/exploits/14089
exploit
-
securityfocus.com
/bid/41184
vdb-entry, exploit
-
packetstormsecurity.org
/1006-exploits/pagedirector-sqladdadmin.txt
exploit
-
vupen.com
/english/advisories/2010/1633
vdb-entry, vendor-advisory
-
secunia.com
/advisories/40367
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59844
vdb-entry
-
osvdb.org
/65830
vdb-entry
Sources
- CVE List CVE-2010-2684
- NVD CVE-2010-2684
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.