Menu

Star on GitHub · 3.2k

CVE-2005-2614

7.5 · HIGH

Discuz!

Published Aug 17, 2005crosscom_olicomEPSS 2.30%

Overview

CVE-2005-2614 is a high-severity vulnerability affecting crosscom_olicom discuz. It was published on August 17, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Discuz! 4.0 rc4 does not properly restrict types of files that are uploaded to the server, which allows remote attackers to execute arbitrary commands via a filename containing ".php.rar" or other multiple extensions that include .php.

Remediation

Check the references section for vendor advisories and patches from crosscom_olicom. Update discuz to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
crosscom_olicomdiscuz0Affected

Frequently asked questions

What is CVE-2005-2614?

CVE-2005-2614 is a high-severity vulnerability affecting crosscom_olicom discuz. It was published on August 17, 2005 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2005-2614?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2005-2614?

Check the references section for vendor advisories and patches from crosscom_olicom. Update discuz to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2005-2614?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2005-2614 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2005

View all