Menu

Star on GitHub · 3.2k

CVE-2009-1463

7.5 · HIGH

Static code injection vulnerability in razorCMS before 0.4 allows remote attackers to inject arbitrary PHP code into any page by saving content as a .php file.

Published Apr 28, 2009razorcmsCWE-94EPSS 1.58%

Overview

CVE-2009-1463 is a high-severity vulnerability affecting razorcms razorcms. It was published on April 28, 2009 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

Static code injection vulnerability in razorCMS before 0.4 allows remote attackers to inject arbitrary PHP code into any page by saving content as a .php file.

Remediation

Check the references section for vendor advisories and patches from razorcms. Update razorcms 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
razorcmsrazorcms0Affected

Frequently asked questions

What is CVE-2009-1463?

CVE-2009-1463 is a high-severity vulnerability affecting razorcms razorcms. It was published on April 28, 2009 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2009-1463?

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-2009-1463?

Check the references section for vendor advisories and patches from razorcms. Update razorcms 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-2009-1463?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2009-1463 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 2009

View all