What is the severity of CVE-2002-1149?

CVE-2002-1149 is classified as a medium severity vulnerability due to the exposure of sensitive information.

How does CVE-2002-1149 affect Invision Board?

CVE-2002-1149 affects Invision Board by allowing unauthorized access to sensitive information through the improper placement of the phpinfo.php file.

How do I fix CVE-2002-1149?

To fix CVE-2002-1149, you should remove the phpinfo.php script from the web root directory and restrict access to sensitive files.

Which versions of Invision Board are affected by CVE-2002-1149?

CVE-2002-1149 affects Invision Board versions 1.0 and 1.0.1.

What information is leaked due to CVE-2002-1149?

CVE-2002-1149 leaks sensitive information such as absolute pathnames, operating system details, and PHP configuration settings.

Vulnerability/
CVE-2002-1149

medium

CWE

NVD-CWE-Other

1/10/2002

8/8/2024

CVE-2002-1149

First published: Tue Oct 01 2002(Updated: )

The installation procedure for Invision Board suggests that users install the phpinfo.php program under the web root, which leaks sensitive information such as absolute pathnames, OS information, and PHP settings.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Invisioncommunity Invision Power Board	=1.0
Invisioncommunity Invision Power Board	=1.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1149?
CVE-2002-1149 is classified as a medium severity vulnerability due to the exposure of sensitive information.
How does CVE-2002-1149 affect Invision Board?
CVE-2002-1149 affects Invision Board by allowing unauthorized access to sensitive information through the improper placement of the phpinfo.php file.
How do I fix CVE-2002-1149?
To fix CVE-2002-1149, you should remove the phpinfo.php script from the web root directory and restrict access to sensitive files.
Which versions of Invision Board are affected by CVE-2002-1149?
CVE-2002-1149 affects Invision Board versions 1.0 and 1.0.1.
What information is leaked due to CVE-2002-1149?
CVE-2002-1149 leaks sensitive information such as absolute pathnames, operating system details, and PHP configuration settings.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/author
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-historical
vendor/invision power services
product/invision board
canonical/invision power services invision board
agent/software-canonical-lookup-request
collector/nvd-index
canonical/invisioncommunity invision power board
version/invisioncommunity invision power board/1.0
version/invisioncommunity invision power board/1.0.1

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-2002-1149?
CVE-2002-1149 is classified as a medium severity vulnerability due to the exposure of sensitive information.
How does CVE-2002-1149 affect Invision Board?
CVE-2002-1149 affects Invision Board by allowing unauthorized access to sensitive information through the improper placement of the phpinfo.php file.
How do I fix CVE-2002-1149?
To fix CVE-2002-1149, you should remove the phpinfo.php script from the web root directory and restrict access to sensitive files.
Which versions of Invision Board are affected by CVE-2002-1149?
CVE-2002-1149 affects Invision Board versions 1.0 and 1.0.1.
What information is leaked due to CVE-2002-1149?
CVE-2002-1149 leaks sensitive information such as absolute pathnames, operating system details, and PHP configuration settings.