What is the severity of CVE-2006-1105?

CVE-2006-1105 has been classified as a high severity vulnerability due to the disclosure of sensitive configuration information.

How do I fix CVE-2006-1105?

To fix CVE-2006-1105, remove or restrict access to the includes/phpinfo.php file in your Pixelpost installation.

Which versions of Pixelpost are affected by CVE-2006-1105?

CVE-2006-1105 affects Pixelpost versions 1.4.3 and earlier, as well as 1.5 beta 1.

What kind of information can be leaked due to CVE-2006-1105?

CVE-2006-1105 can lead to the leakage of sensitive configuration information such as server environment variables.

Is there a patch available for CVE-2006-1105?

There is no specific patch for CVE-2006-1105; it is recommended to apply protective measures by securing the affected file.

Vulnerability/
CVE-2006-1105

medium

CWE

NVD-CWE-Other

9/3/2006

7/8/2024

CVE-2006-1105

First published: Thu Mar 09 2006(Updated: )

Pixelpost 1.5 beta 1 and earlier allows remote attackers to obtain configuration information via a direct request to includes/phpinfo.php, which calls the phpinfo function. NOTE: the vendor has disputed some issues from the original disclosure, but due to the vagueness of the dispute, it is not clear whether the vendor is disputing this particular issue.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Pixelpost	=1.4.3
Pixelpost	=1.5_beta1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-1105?
CVE-2006-1105 has been classified as a high severity vulnerability due to the disclosure of sensitive configuration information.
How do I fix CVE-2006-1105?
To fix CVE-2006-1105, remove or restrict access to the includes/phpinfo.php file in your Pixelpost installation.
Which versions of Pixelpost are affected by CVE-2006-1105?
CVE-2006-1105 affects Pixelpost versions 1.4.3 and earlier, as well as 1.5 beta 1.
What kind of information can be leaked due to CVE-2006-1105?
CVE-2006-1105 can lead to the leakage of sensitive configuration information such as server environment variables.
Is there a patch available for CVE-2006-1105?
There is no specific patch for CVE-2006-1105; it is recommended to apply protective measures by securing the affected file.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/weakness
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/pixelpost
canonical/pixelpost
version/pixelpost/1.4.3
version/pixelpost/1.5_beta1

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-2006-1105?
CVE-2006-1105 has been classified as a high severity vulnerability due to the disclosure of sensitive configuration information.
How do I fix CVE-2006-1105?
To fix CVE-2006-1105, remove or restrict access to the includes/phpinfo.php file in your Pixelpost installation.
Which versions of Pixelpost are affected by CVE-2006-1105?
CVE-2006-1105 affects Pixelpost versions 1.4.3 and earlier, as well as 1.5 beta 1.
What kind of information can be leaked due to CVE-2006-1105?
CVE-2006-1105 can lead to the leakage of sensitive configuration information such as server environment variables.
Is there a patch available for CVE-2006-1105?
There is no specific patch for CVE-2006-1105; it is recommended to apply protective measures by securing the affected file.