What is CVE-2008-4793?

CVE-2008-4793 is a high-severity security vulnerability in drupal/drupal (composer), affecting versions >= 5.0, < 5.11. It is fixed in 5.11.

Which versions of drupal/drupal are affected by CVE-2008-4793?

drupal/drupal (composer) versions >= 5.0, < 5.11 is affected.

Is there a fix for CVE-2008-4793?

Yes. CVE-2008-4793 is fixed in 5.11. Upgrade to this version or later.

Is CVE-2008-4793 exploitable, and should I be worried?

Whether CVE-2008-4793 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2008-4793 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2008-4793 in drupal/drupal

Q: Which versions of drupal/drupal are affected by CVE-2008-4793?

drupal/drupal (composer) versions >= 5.0, < 5.11 is affected.

Q: Is there a fix for CVE-2008-4793?

Yes. CVE-2008-4793 is fixed in 5.11. Upgrade to this version or later.

Q: Is CVE-2008-4793 exploitable, and should I be worried?

Whether CVE-2008-4793 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2008-4793 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2008-4793?

Upgrade drupal/drupal to 5.11 or later.

Summary

Drupal Node Validation Bypass in the node module API

The node module API in Drupal 5.x before 5.11 allows remote attackers to bypass node validation and have unspecified other impact via unknown vectors related to contributed modules.

Impact

Affected versions

drupal/drupal (>= 5.0, < 5.11)

Security releases

drupal/drupal → 5.11 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade drupal/drupal to 5.11 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2008-4793? CVE-2008-4793 is a high-severity security vulnerability in drupal/drupal (composer), affecting versions >= 5.0, < 5.11. It is fixed in 5.11.
Which versions of drupal/drupal are affected by CVE-2008-4793? drupal/drupal (composer) versions >= 5.0, < 5.11 is affected.
Is there a fix for CVE-2008-4793? Yes. CVE-2008-4793 is fixed in 5.11. Upgrade to this version or later.
Is CVE-2008-4793 exploitable, and should I be worried? Whether CVE-2008-4793 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2008-4793 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2008-4793? Upgrade drupal/drupal to 5.11 or later.

Other vulnerabilities in drupal/drupal

CVE-IDSeverityPackage summary

CVE-2024-55636Lowdrupal/core: Drupal core contains a potential PHP Object Injection vulnerability CVE-2024-55638Highdrupal/core: Drupal core contains a potential PHP Object Injection vulnerability CVE-2024-55637Highdrupal/core: Drupal core contains a potential PHP Object Injection vulnerability CVE-2024-55634Mediumdrupal/core: Drupal core Access bypass CVE-2024-12393Mediumdrupal/core: Drupal Core Cross-Site Scripting (XSS)