high
7.5
CWE
NVD-CWE-Other
Advisory Published
CVE Published
Updated

CVE-2004-2044

First published: Tue Jun 01 2004(Updated: )

PHP-Nuke 7.3, and other products that use the PHP-Nuke codebase such as the Nuke Cops betaNC PHP-Nuke Bundle, OSCNukeLite 3.1, and OSC2Nuke 7x do not properly use the eregi() PHP function with $_SERVER['PHP_SELF'] to identify the calling script, which allows remote attackers to directly access scripts, obtain path information via a PHP error message, and possibly gain access, as demonstrated using an HTTP request that contains the "admin.php" string.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
PHP-Nuke=5.3.1
PHP-Nuke=5.1
PHP-Nuke=6.5_beta1
PHP-Nuke=6.5
PHP-Nuke=7.0
osCommerce=7x_1.0
PHP-Nuke=5.0
PHP-Nuke=7.2
PHP-Nuke=5.5
PHP-Nuke=7.0_final
PHP-Nuke=5.4
PHP-Nuke=6.5_rc2
PHP-Nuke=5.2a
PHP-Nuke=7.3
PHP-Nuke=6.5_rc3
PHP-Nuke=5.0.1
PHP-Nuke=5.2
PHP-Nuke=bundle
PHP-Nuke=5.6
PHP-Nuke=6.0
PHP-Nuke=6.5_final
PHP-Nuke=6.7
PHP-Nuke=6.6
PHP-Nuke=6.9
PHP-Nuke=7.1
PHP-Nuke=6.5_rc1
Trustix Secure Linux=2.0
Trustix Secure Linux=2.1

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-2004-2044?

    CVE-2004-2044 is considered a critical vulnerability as it allows remote attackers to exploit improper use of the eregi() function in PHP-Nuke.

  • How do I fix CVE-2004-2044?

    To fix CVE-2004-2044, you should update your PHP-Nuke installation to a secure version that properly validates the $_SERVER['PHP_SELF'] input.

  • What are the affected versions of PHP-Nuke for CVE-2004-2044?

    Affected versions include PHP-Nuke 7.3 and earlier versions, along with other products that use the PHP-Nuke codebase.

  • Can CVE-2004-2044 lead to unauthorized access?

    Yes, CVE-2004-2044 can lead to unauthorized access where attackers can directly interact with scripts.

  • Is there a workaround for CVE-2004-2044?

    A possible workaround includes implementing input validation and sanitization on the $_SERVER['PHP_SELF'] variable to mitigate the risk.

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