CVE-2005-3882
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and...
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
Exploit likelihood
What each source reports
NVD Score used
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
- Record
CVE-2005-3882- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
- Record
CVE-2005-3882- Updated
- 2026-11-02
EUVDEUVD-2005-3877 No score
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
- Record
EUVD-2005-3877- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-x6h9-x5h5-8pwq No score
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and...
SQL injection vulnerability in answer.php in FAQSystems FAQRing Knowledge Base Software 3.0 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.
- Record
GHSA-x6h9-x5h5-8pwq- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | FAQRing 3.0 - 'answer.php' SQL Injection | 2005-11-30 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2005-3882 is a high vulnerability (CVSS 7.5) in Faqsystems Faqring Knowledge Base Software, published November 29, 2005. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 1.12%, the 66th percentile. No source names a fixed version.
