CVE-2010-4955 json
SQL injection vulnerability in board/board.php in APBoard Developers APBoard 2.1.0 and earlier allows remote attackers to execute arbitrary…
published 15y ago modified 4mo ago also EUVD-2010-4919
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in board/board.php in APBoard Developers APBoard 2.1.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter, a different vector than CVE-2006-3078.
Is CVE-2010-4955 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-14559)
- Published
Exploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14559 APBoard 2.1.0 - 'board.php?id' SQL Injection webapps, 2010-08-05
- securityfocus.com http://www.securityfocus.com/bid/42262 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1008-exploits/apboard-sql.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/14559
exploit
-
securityfocus.com
/bid/42262
vdb-entry, exploit
-
packetstormsecurity.org
/1008-exploits/apboard-sql.txt
exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/60935
vdb-entry
-
securityreason.com
/securityalert/8467
third-party-advisory
Sources
- CVE List CVE-2010-4955
- NVD CVE-2010-4955
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.