Skip to content
Fencer Intel
high 7.5

CVE-2010-5032 json

SQL injection vulnerability in the BF Quiz (com_bfquiztrial) component before 1.3.1 for Joomla!

published 15y ago modified 4mo ago also EUVD-2010-4996

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
2
Exploit-DB

Summary

SQL injection vulnerability in the BF Quiz (com_bfquiztrial) component before 1.3.1 for Joomla! allows remote attackers to execute arbitrary SQL commands via the catid parameter in a bfquiztrial action to index.php.

Patch / fix

Is CVE-2010-5032 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 Fencer

Timeline

  1. First public exploit (EDB-12780)
  2. Published

Exploit prediction

1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-12796 Joomla! Component BF Quiz 1.0 - SQL Injection (2) webapps, 2010-05-29
  • EDB-12780 Joomla! Component BF Quiz 1.3.0 - SQL Injection (1) webapps, 2010-05-28
  • xenuser.org http://xenuser.org/documents/security/joomla_com_bfquiz_sqli.txt referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.org http://packetstormsecurity.org/1005-exploits/joomla_com_bfquiz_sploit.py.txt referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.org http://www.packetstormsecurity.org/1005-exploits/joomlabfquiz-sql.txt referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://osvdb.org/65001 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/40435 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

Sources

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.