What is the severity of CVE-2006-6217?

CVE-2006-6217 is considered a critical vulnerability due to its ability to allow remote attackers to execute arbitrary PHP code.

How do I fix CVE-2006-6217?

To fix CVE-2006-6217, update the Mermaid module for PHP-Nuke to a version that is not vulnerable or apply appropriate input validation and sanitization to the module_name parameter.

What systems are affected by CVE-2006-6217?

CVE-2006-6217 specifically affects the Mermaid module version 1.2 of PHP-Nuke.

What type of vulnerability is CVE-2006-6217?

CVE-2006-6217 is classified as a remote file inclusion vulnerability.

How can attackers exploit CVE-2006-6217?

Attackers can exploit CVE-2006-6217 by sending a specially crafted request with a malicious URL in the module_name parameter.

Vulnerability/
CVE-2006-6217

high

7.5

CWE

NVD-CWE-Other

1/12/2006

7/8/2024

CVE-2006-6217

First published: Fri Dec 01 2006(Updated: )

PHP remote file inclusion vulnerability in formdisp.php in the Mermaid 1.2 module for PHP-Nuke allows remote attackers to execute arbitrary PHP code via a URL in the module_name parameter.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Php-nuke Mermaid Module	=1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-6217?
CVE-2006-6217 is considered a critical vulnerability due to its ability to allow remote attackers to execute arbitrary PHP code.
How do I fix CVE-2006-6217?
To fix CVE-2006-6217, update the Mermaid module for PHP-Nuke to a version that is not vulnerable or apply appropriate input validation and sanitization to the module_name parameter.
What systems are affected by CVE-2006-6217?
CVE-2006-6217 specifically affects the Mermaid module version 1.2 of PHP-Nuke.
What type of vulnerability is CVE-2006-6217?
CVE-2006-6217 is classified as a remote file inclusion vulnerability.
How can attackers exploit CVE-2006-6217?
Attackers can exploit CVE-2006-6217 by sending a specially crafted request with a malicious URL in the module_name parameter.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/weakness
agent/last-modified-date
agent/tags
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/php-nuke
canonical/php-nuke mermaid module
version/php-nuke mermaid module/1.2

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-6217?
CVE-2006-6217 is considered a critical vulnerability due to its ability to allow remote attackers to execute arbitrary PHP code.
How do I fix CVE-2006-6217?
To fix CVE-2006-6217, update the Mermaid module for PHP-Nuke to a version that is not vulnerable or apply appropriate input validation and sanitization to the module_name parameter.
What systems are affected by CVE-2006-6217?
CVE-2006-6217 specifically affects the Mermaid module version 1.2 of PHP-Nuke.
What type of vulnerability is CVE-2006-6217?
CVE-2006-6217 is classified as a remote file inclusion vulnerability.
How can attackers exploit CVE-2006-6217?
Attackers can exploit CVE-2006-6217 by sending a specially crafted request with a malicious URL in the module_name parameter.