How severe is CVE-2005-2691?

CVE-2005-2691 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-2691 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-2691?

CVE-2005-2691 primarily affects Runcms. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-2691?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-2691 published?

CVE-2005-2691 was published on 2005-08-24 and last updated on 2026-06-16.

CVE-2005-2691

CVE-2005-2691 is a high-severity vulnerability in Runcms with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (81st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Runcms
Published: 2005-08-24
Last modified: 2026-06-16

Description

includes/common.php in RunCMS 1.2 and earlier calls the extract function with EXTR_OVERWRITE on HTTP POST variables, which allows remote attackers to overwrite arbitrary variables, possibly allowing execution of arbitrary code.

Frequently asked questions

What is CVE-2005-2691?: includes/common.php in RunCMS 1.2 and earlier calls the extract function with EXTR_OVERWRITE on HTTP POST variables, which allows remote attackers to overwrite arbitrary variables, possibly allowing execution of arbitrary code.
How severe is CVE-2005-2691?: CVE-2005-2691 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-2691 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-2691?: CVE-2005-2691 primarily affects Runcms. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-2691?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-2691 published?: CVE-2005-2691 was published on 2005-08-24 and last updated on 2026-06-16.

References

Affected products (3)

cpe:2.3:a:runcms:runcms:1.1:*:*:*:*:*:*:*
cpe:2.3:a:runcms:runcms:1.1a:*:*:*:*:*:*:*
cpe:2.3:a:runcms:runcms:1.2:*:*:*:*:*:*:*

More vulnerabilities in Runcms

CVE-2007-5535 — Critical (CVSS 10.0): Unspecified vulnerability in newbb_plus in RunCms 1.5.2 has unknown impact and attack vectors.
CVE-2007-2539 — High (CVSS 7.8): The show_files function in RunCms 1.5.2 and earlier allows remote attackers to obtain sensitive information (file…
CVE-2006-1793 — High (CVSS 7.6): Directory traversal vulnerability in runCMS 1.2 and earlier allows remote attackers to read arbitrary files via the…
CVE-2008-3354 — High (CVSS 7.5): Multiple PHP remote file inclusion vulnerabilities in the Newbb Plus (newbb_plus) module 0.93 in RunCMS 1.6.1 allow…
CVE-2008-1551 — High (CVSS 7.5): SQL injection vulnerability in viewcat.php in the Photo 3.02 module for RunCMS allows remote attackers to execute…
CVE-2008-0224 — High (CVSS 7.5): SQL injection vulnerability in index.php in the Newbb_plus 0.92 and earlier module in RunCMS 1.6.1 allows remote…

All CVEs affecting Runcms →