medium
5
CWE
264
Advisory Published
Updated

CVE-2009-4851

First published: Fri May 07 2010(Updated: )

The activation resend function in the Profiles module in XOOPS before 2.4.1 sends activation codes in response to arbitrary activation requests, which allows remote attackers to bypass administrative approval via a request involving activate.php.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Xoops<=2.4.0
Xoops=1.0
Xoops=1.0_rc1
Xoops=1.0_rc3
Xoops=1.0_rc3.0.5
Xoops=1.3.5
Xoops=1.3.6
Xoops=1.3.7
Xoops=1.3.8
Xoops=1.3.9
Xoops=1.3.10
Xoops=2.0.0
Xoops=2.0.0_rc1
Xoops=2.0.0_rc2
Xoops=2.0.0_rc3
Xoops=2.0.1
Xoops=2.0.2
Xoops=2.0.3
Xoops=2.0.4
Xoops=2.0.5.1
Xoops=2.0.5.2
Xoops=2.0.5_rc
Xoops=2.0.6
Xoops=2.0.7
Xoops=2.0.7.1
Xoops=2.0.7.2
Xoops=2.0.7.3
Xoops=2.0.9
Xoops=2.0.9.2
Xoops=2.0.9.3
Xoops=2.0.10
Xoops=2.0.10_rc
Xoops=2.0.11
Xoops=2.0.12
Xoops=2.0.12a
Xoops=2.0.13
Xoops=2.0.13.1
Xoops=2.0.13.2
Xoops=2.0.14
Xoops=2.0.14-rc1
Xoops=2.0.15
Xoops=2.0.16
Xoops=2.0.17
Xoops=2.0.17.1
Xoops=2.0.18
Xoops=2.0.18.1
Xoops=2.3.0
Xoops=2.3.0_alpha_3
Xoops=2.3.0_alpha1
Xoops=2.3.0_alpha2
Xoops=2.3.0_beta
Xoops=2.3.0_rc
Xoops=2.3.0_rc2
Xoops=2.3.0_rc3
Xoops=2.3.1
Xoops=2.3.1_rc
Xoops=2.3.2a
Xoops=2.3.2b
Xoops=2.3.3
Xoops=2.4.0_beta_1
Xoops=2.4.0_beta_2
Xoops=2.4.0_rc
<=2.4.0
=1.0
=1.0_rc1
=1.0_rc3
=1.0_rc3.0.5
=1.3.5
=1.3.6
=1.3.7
=1.3.8
=1.3.9
=1.3.10
=2.0.0
=2.0.0_rc1
=2.0.0_rc2
=2.0.0_rc3
=2.0.1
=2.0.2
=2.0.3
=2.0.4
=2.0.5.1
=2.0.5.2
=2.0.5_rc
=2.0.6
=2.0.7
=2.0.7.1
=2.0.7.2
=2.0.7.3
=2.0.9
=2.0.9.2
=2.0.9.3
=2.0.10
=2.0.10_rc
=2.0.11
=2.0.12
=2.0.12a
=2.0.13
=2.0.13.1
=2.0.13.2
=2.0.14
=2.0.14-rc1
=2.0.15
=2.0.16
=2.0.17
=2.0.17.1
=2.0.18
=2.0.18.1
=2.3.0
=2.3.0_alpha_3
=2.3.0_alpha1
=2.3.0_alpha2
=2.3.0_beta
=2.3.0_rc
=2.3.0_rc2
=2.3.0_rc3
=2.3.1
=2.3.1_rc
=2.3.2a
=2.3.2b
=2.3.3
=2.4.0_beta_1
=2.4.0_beta_2
=2.4.0_rc

Remedy

http://www.xoops.org/modules/news/article.php?storyid=5096

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-2009-4851?

    CVE-2009-4851 is considered a high-severity vulnerability as it allows remote attackers to bypass administrative approval.

  • How do I fix CVE-2009-4851?

    To mitigate CVE-2009-4851, upgrading to XOOPS version 2.4.1 or later is recommended.

  • What is the impact of CVE-2009-4851 on affected software?

    CVE-2009-4851 can lead to unauthorized account activation by bypassing the intended administrative approval process.

  • Which versions of XOOPS are affected by CVE-2009-4851?

    CVE-2009-4851 affects XOOPS versions prior to 2.4.1, including several earlier versions.

  • Is there a workaround for CVE-2009-4851?

    A temporary workaround for CVE-2009-4851 could involve restricting access to the activation function until a suitable upgrade 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