What is the severity of CVE-2001-1471?

CVE-2001-1471 has a high severity rating due to its ability to allow remote code execution.

How do I fix CVE-2001-1471?

To fix CVE-2001-1471, upgrade phpBB to version 1.4.1 or later to ensure that language value validation is properly implemented.

Who is affected by CVE-2001-1471?

CVE-2001-1471 affects all versions of phpBB up to and including version 1.4.0.

What exploits are associated with CVE-2001-1471?

Exploits associated with CVE-2001-1471 can lead to arbitrary PHP code execution by leveraging improperly initialized variables.

Is there a workaround for CVE-2001-1471?

A temporary workaround for CVE-2001-1471 includes restricting user access to the prefs.php script until the software is updated.

Vulnerability/
CVE-2001-1471

high

8.8

CWE

NVD-CWE-Other 665

31/7/2001

21/4/2005

8/8/2024

CVE-2001-1471

First published: Tue Jul 31 2001(Updated: )

prefs.php in phpBB 1.4.0 and earlier allows remote authenticated users to execute arbitrary PHP code via an invalid language value, which prevents the variables (1) $l_statsblock in prefs.php or (2) $l_privnotify in auth.php from being properly initialized, which can be modified by the user and later used in an eval statement.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Phpbb Group Phpbb	=1.2.1
Phpbb Group Phpbb	=1.0.0
Phpbb Group Phpbb	=1.2.0
Phpbb Group Phpbb	=1.4.0
phpBB	<=1.4.0

Remedy

http://www.securityfocus.com/bid/3167

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-1471?
CVE-2001-1471 has a high severity rating due to its ability to allow remote code execution.
How do I fix CVE-2001-1471?
To fix CVE-2001-1471, upgrade phpBB to version 1.4.1 or later to ensure that language value validation is properly implemented.
Who is affected by CVE-2001-1471?
CVE-2001-1471 affects all versions of phpBB up to and including version 1.4.0.
What exploits are associated with CVE-2001-1471?
Exploits associated with CVE-2001-1471 can lead to arbitrary PHP code execution by leveraging improperly initialized variables.
Is there a workaround for CVE-2001-1471?
A temporary workaround for CVE-2001-1471 includes restricting user access to the prefs.php script until the software is updated.

collector/nvd-historical
collector/nvd-index
agent/type
agent/first-publish-date
agent/remedy
agent/severity
agent/weakness
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/phpbb group
canonical/phpbb group phpbb
version/phpbb group phpbb/1.2.1
version/phpbb group phpbb/1.0.0
version/phpbb group phpbb/1.2.0
version/phpbb group phpbb/1.4.0
vendor/phpbb
canonical/phpbb
version/phpbb/1.4.0

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.

Frequently Asked Questions

What is the severity of CVE-2001-1471?
CVE-2001-1471 has a high severity rating due to its ability to allow remote code execution.
How do I fix CVE-2001-1471?
To fix CVE-2001-1471, upgrade phpBB to version 1.4.1 or later to ensure that language value validation is properly implemented.
Who is affected by CVE-2001-1471?
CVE-2001-1471 affects all versions of phpBB up to and including version 1.4.0.
What exploits are associated with CVE-2001-1471?
Exploits associated with CVE-2001-1471 can lead to arbitrary PHP code execution by leveraging improperly initialized variables.
Is there a workaround for CVE-2001-1471?
A temporary workaround for CVE-2001-1471 includes restricting user access to the prefs.php script until the software is updated.