CVE-2005-3020: XSS

Published Sep 21, 2005
·
Updated

Multiple cross-site scripting (XSS) vulnerabilities in vBulletin before 3.0.9 allow remote attackers to inject arbitrary web script or HTML via the (1) group parameter to css.php, (2) redirect parameter to index.php, (3) email parameter to user.php, (4) goto parameter to language.php, (5) orderby parameter to modlog.php, and the (6) hex, (7) rgb, or (8) expandset parameter to template.php.

Affected Software

35 affected components
Jelsoft vBulletin=2.2.0
Jelsoft vBulletin=2.0_rc2
Jelsoft vBulletin=3.0.4
Jelsoft vBulletin=3.0_beta_6
Jelsoft vBulletin=2.3.0
Jelsoft vBulletin=2.3.2
Jelsoft vBulletin=3.0.1
Jelsoft vBulletin=2.0_rc3
Jelsoft vBulletin=3.0.6
Jelsoft vBulletin=2.2.1
Jelsoft vBulletin=2.2.7
Jelsoft vBulletin=2.0.3
Jelsoft vBulletin=3.0_beta_7
Jelsoft vBulletin=3.0.9
Jelsoft vBulletin=3.0_beta_3
Jelsoft vBulletin=2.2.4
Jelsoft vBulletin=3.0_beta_2
Jelsoft vBulletin=2.2.2
Jelsoft vBulletin=2.2.5
Jelsoft vBulletin=2.2.6
Jelsoft vBulletin=3.0.2
Jelsoft vBulletin=3.0_gamma
Jelsoft vBulletin=2.2.9
Jelsoft vBulletin=3.0.7
Jelsoft vBulletin=3.0.8
Jelsoft vBulletin=3.0_beta_4
Jelsoft vBulletin=3.0.3
Jelsoft vBulletin=1.0.1
Jelsoft vBulletin=3.0.5
Jelsoft vBulletin=2.2.8
Jelsoft vBulletin=2.3.4
Jelsoft vBulletin=2.2.3
Jelsoft vBulletin=3.0
Jelsoft vBulletin=3.0_beta_5
Jelsoft vBulletin=2.3.3

Event History

Sep 21, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2005-3020?

CVE-2005-3020 is considered a moderate severity vulnerability due to the potential for cross-site scripting attacks.

2

How do I fix CVE-2005-3020?

To fix CVE-2005-3020, you should upgrade to vBulletin version 3.0.9 or later, which addresses the XSS vulnerabilities.

3

What versions of vBulletin are affected by CVE-2005-3020?

CVE-2005-3020 affects multiple versions of vBulletin including 2.0_rc2, 2.2.0, and versions up to 3.0.8.

4

Can CVE-2005-3020 lead to data theft?

Yes, CVE-2005-3020 can allow attackers to inject malicious scripts, which could lead to data theft or session hijacking.

5

Is there a workaround for CVE-2005-3020?

While upgrading is the recommended solution for CVE-2005-3020, disabling certain features or sanitizing user inputs can serve as temporary workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203