critical
9.3
CWE
264
Advisory Published
Updated

CVE-2006-1726

First published: Fri Apr 14 2006(Updated: )

Unspecified vulnerability in Firefox and Thunderbird 1.5 before 1.5.0.2, and SeaMonkey before 1.0.1, allows remote attackers to bypass the js_ValueToFunctionObject check and execute arbitrary code via unknown vectors involving setTimeout and Firefox' ForEach method.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Mozilla Firefox=1.5-beta2
Mozilla Thunderbird=1.0.7
Mozilla Firefox=1.0.2
Mozilla SeaMonkey=1.0-beta
Mozilla Firefox=1.5-beta1
Mozilla Firefox=1.5
Mozilla Firefox=1.0.4
Mozilla Firefox=1.0.7
Mozilla Thunderbird=1.0
Mozilla Thunderbird=1.0.1
Mozilla Thunderbird=1.5-beta2
Mozilla SeaMonkey=1.0
Mozilla Thunderbird=1.0.2
Mozilla Firefox=1.0
Mozilla Thunderbird=1.5
Mozilla Firefox=1.0.1
Mozilla Firefox=preview_release
Mozilla Thunderbird=1.0.4
Mozilla Thunderbird=1.0.3
Mozilla Firefox=1.0.3
Mozilla Thunderbird=1.0.6
Mozilla Thunderbird=1.0.5-beta
Mozilla Thunderbird=1.0.5
Mozilla Firefox=1.5.0.1
Mozilla Firefox=1.0.5
Mozilla Firefox=1.0.6

Remedy

http://www.mozilla.org/security/announce/2006/mfsa2006-28.html

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-2006-1726?

    CVE-2006-1726 is classified as a critical vulnerability due to its potential to allow remote code execution.

  • How do I fix CVE-2006-1726?

    To mitigate CVE-2006-1726, users should upgrade to the latest versions of Firefox, Thunderbird, or SeaMonkey that contain the security patches.

  • Which versions are affected by CVE-2006-1726?

    CVE-2006-1726 affects Firefox versions prior to 1.5.0.2, Thunderbird versions prior to 1.0.8, and SeaMonkey versions prior to 1.0.1.

  • What type of attack does CVE-2006-1726 enable?

    CVE-2006-1726 allows remote attackers to execute arbitrary code through a flaw in the setTimeout method.

  • Is there a workaround for CVE-2006-1726?

    No specific workaround is available for CVE-2006-1726; the best course of action is to update to a patched version.

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