What is the severity of CVE-2006-2890?

CVE-2006-2890 is considered a critical vulnerability due to the potential for unauthorized administrative access.

How do I fix CVE-2006-2890?

To fix CVE-2006-2890, disable register_globals in your PHP configuration and upgrade to the latest version of Pixelpost.

What types of attacks can exploit CVE-2006-2890?

CVE-2006-2890 can be exploited to gain administrator privileges, allowing attackers to modify or delete content.

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

CVE-2006-2890 affects Pixelpost versions 1.5rc1 and earlier.

Is there a known workaround for CVE-2006-2890?

A known workaround for CVE-2006-2890 is to ensure register_globals is disabled on the server.

Vulnerability/
CVE-2006-2890

medium

5.1

CWE

NVD-CWE-Other

7/6/2006

7/8/2024

CVE-2006-2890

First published: Wed Jun 07 2006(Updated: )

Pixelpost 1-5rc1-2 and earlier, when register_globals is enabled, allows remote attackers to gain administrator privileges and conduct other attacks by setting the _SESSION["pixelpost_admin"] parameter to 1 in calls to admin scripts such as admin/view_info.php.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Pixelpost	=1.5_rc1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-2890?
CVE-2006-2890 is considered a critical vulnerability due to the potential for unauthorized administrative access.
How do I fix CVE-2006-2890?
To fix CVE-2006-2890, disable register_globals in your PHP configuration and upgrade to the latest version of Pixelpost.
What types of attacks can exploit CVE-2006-2890?
CVE-2006-2890 can be exploited to gain administrator privileges, allowing attackers to modify or delete content.
Which versions of Pixelpost are affected by CVE-2006-2890?
CVE-2006-2890 affects Pixelpost versions 1.5rc1 and earlier.
Is there a known workaround for CVE-2006-2890?
A known workaround for CVE-2006-2890 is to ensure register_globals is disabled on the server.

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

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-2890?
CVE-2006-2890 is considered a critical vulnerability due to the potential for unauthorized administrative access.
How do I fix CVE-2006-2890?
To fix CVE-2006-2890, disable register_globals in your PHP configuration and upgrade to the latest version of Pixelpost.
What types of attacks can exploit CVE-2006-2890?
CVE-2006-2890 can be exploited to gain administrator privileges, allowing attackers to modify or delete content.
Which versions of Pixelpost are affected by CVE-2006-2890?
CVE-2006-2890 affects Pixelpost versions 1.5rc1 and earlier.
Is there a known workaround for CVE-2006-2890?
A known workaround for CVE-2006-2890 is to ensure register_globals is disabled on the server.