medium
4.3
CWE
79
Advisory Published
Updated

CVE-2011-1689: XSS

First published: Fri Apr 22 2011(Updated: )

Multiple cross-site scripting (XSS) vulnerabilities in Best Practical Solutions RT 2.0.0 through 3.6.10, 3.8.0 through 3.8.9, and 4.0.0rc through 4.0.0rc7 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Best Practical Solutions Request Tracker=3.0.4
Best Practical Solutions Request Tracker=2.0.7
Best Practical Solutions Request Tracker=3.0.8
Best Practical Solutions Request Tracker=2.0.6
Best Practical Solutions Request Tracker=3.4.5
Best Practical Solutions Request Tracker=3.0.2
Best Practical Solutions Request Tracker=2.0.14
Best Practical Solutions Request Tracker=3.6.7
Best Practical Solutions Request Tracker=3.6.2
Best Practical Solutions Request Tracker=3.2.2
Best Practical Solutions Request Tracker=3.6.3
Best Practical Solutions Request Tracker=3.0.11
Best Practical Solutions Request Tracker=2.0.15
Best Practical Solutions Request Tracker=3.6.0
Best Practical Solutions Request Tracker=2.0.5.3
Best Practical Solutions Request Tracker=3.4.0
Best Practical Solutions Request Tracker=2.0.8.2
Best Practical Solutions Request Tracker=2.0.13
Best Practical Solutions Request Tracker=3.0.10
Best Practical Solutions Request Tracker=2.0.11
Best Practical Solutions Request Tracker=2.0.0
Best Practical Solutions Request Tracker=3.6.10
Best Practical Solutions Request Tracker=2.0.1
Best Practical Solutions Request Tracker=3.2.3
Best Practical Solutions Request Tracker=2.0.2
Best Practical Solutions Request Tracker=3.0.5
Best Practical Solutions Request Tracker=3.2.0
Best Practical Solutions Request Tracker=3.0.0
Best Practical Solutions Request Tracker=3.4.6
Best Practical Solutions Request Tracker=3.0.3
Best Practical Solutions Request Tracker=3.4.3
Best Practical Solutions Request Tracker=2.0.8
Best Practical Solutions Request Tracker=3.6.9
Best Practical Solutions Request Tracker=3.6.6
Best Practical Solutions Request Tracker=2.0.5
Best Practical Solutions Request Tracker=3.6.5
Best Practical Solutions Request Tracker=3.0.1
Best Practical Solutions Request Tracker=3.2.1
Best Practical Solutions Request Tracker=2.0.5.1
Best Practical Solutions Request Tracker=3.4.4
Best Practical Solutions Request Tracker=3.6.8
Best Practical Solutions Request Tracker=3.0.6
Best Practical Solutions Request Tracker=3.0.7
Best Practical Solutions Request Tracker=3.0.7.1
Best Practical Solutions Request Tracker=3.0.12
Best Practical Solutions Request Tracker=3.0.9
Best Practical Solutions Request Tracker=3.6.1
Best Practical Solutions Request Tracker=3.4.1
Best Practical Solutions Request Tracker=3.6.4
Best Practical Solutions Request Tracker=2.0.4
Best Practical Solutions Request Tracker=2.0.9
Best Practical Solutions Request Tracker=2.0.3
Best Practical Solutions Request Tracker=2.0.12
Best Practical Solutions Request Tracker=3.4.2
Best Practical Solutions Request Tracker=3.8.7
Best Practical Solutions Request Tracker=3.8.9-rc2
Best Practical Solutions Request Tracker=3.8.8-rc2
Best Practical Solutions Request Tracker=3.8.9-rc1
Best Practical Solutions Request Tracker=3.8.2
Best Practical Solutions Request Tracker=3.8.8-rc4
Best Practical Solutions Request Tracker=3.8.0
Best Practical Solutions Request Tracker=3.8.9
Best Practical Solutions Request Tracker=3.8.8-rc3
Best Practical Solutions Request Tracker=3.8.9-rc3
Best Practical Solutions Request Tracker=3.8.5
Best Practical Solutions Request Tracker=3.8.6-rc1
Best Practical Solutions Request Tracker=3.8.8
Best Practical Solutions Request Tracker=3.8.3
Best Practical Solutions Request Tracker=3.8.6
Best Practical Solutions Request Tracker=3.8.1
Best Practical Solutions Request Tracker=3.8.4
Best Practical Solutions Request Tracker=3.8.7-rc1
Best Practical Solutions Request Tracker=4.0.0-rc4
Best Practical Solutions Request Tracker=4.0.0-rc7
Best Practical Solutions Request Tracker=4.0.0-rc3
Best Practical Solutions Request Tracker=4.0.0-rc6
Best Practical Solutions Request Tracker=4.0.0-rc5
Best Practical Solutions Request Tracker=4.0.0-rc2
Best Practical Solutions Request Tracker=4.0.0-rc1

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2011-April/000187.html

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2011-April/000188.html

Remedy

http://lists.bestpractical.com/pipermail/rt-announce/2011-April/000189.html

Remedy

https://bugzilla.redhat.com/show_bug.cgi?id=696795

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-1689?

    The severity of CVE-2011-1689 is classified as high due to its potential to allow remote attackers to execute arbitrary scripts.

  • How do I fix CVE-2011-1689?

    To fix CVE-2011-1689, upgrade to the latest version of Best Practical Solutions RT that addresses the XSS vulnerabilities.

  • Who is affected by CVE-2011-1689?

    CVE-2011-1689 affects multiple versions of Best Practical Solutions RT, specifically versions 2.0.0 through 4.0.0rc7.

  • What types of attacks does CVE-2011-1689 allow?

    CVE-2011-1689 allows cross-site scripting (XSS) attacks, which can enable attackers to inject arbitrary web scripts or HTML.

  • Is there a workaround for CVE-2011-1689?

    While the best solution is to upgrade, temporarily disabling scripting features may reduce risk until a patch is applied.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203