What is CVE-2010-3094?

CVE-2010-3094 is a low-severity cross-site scripting (XSS) vulnerability in drupal/drupal (composer), affecting versions >= 6.0, < 6.18. It is fixed in 6.18. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of drupal/drupal are affected by CVE-2010-3094?

drupal/drupal (composer) versions >= 6.0, < 6.18 is affected.

Is there a fix for CVE-2010-3094?

Yes. CVE-2010-3094 is fixed in 6.18. Upgrade to this version or later.

Is CVE-2010-3094 exploitable, and should I be worried?

Whether CVE-2010-3094 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-2010-3094 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-2010-3094 in drupal/drupal

Q: Which versions of drupal/drupal are affected by CVE-2010-3094?

drupal/drupal (composer) versions >= 6.0, < 6.18 is affected.

Q: Is there a fix for CVE-2010-3094?

Yes. CVE-2010-3094 is fixed in 6.18. Upgrade to this version or later.

Q: Is CVE-2010-3094 exploitable, and should I be worried?

Whether CVE-2010-3094 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-2010-3094 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-2010-3094?

Upgrade drupal/drupal to 6.18 or later.

Summary

Drupal cross-site scripting vulnerability via actions feature and trigger module

Multiple cross-site scripting (XSS) vulnerabilities in Drupal 6.x before 6.18 allow remote authenticated users with certain privileges to inject arbitrary web script or HTML via (1) an action description, (2) an action message, (3) a node, or (4) a taxonomy term, related to the actions feature and the trigger module.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

drupal/drupal (>= 6.0, < 6.18)

Security releases

drupal/drupal → 6.18 (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 6.18 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-2010-3094? CVE-2010-3094 is a low-severity cross-site scripting (XSS) vulnerability in drupal/drupal (composer), affecting versions >= 6.0, < 6.18. It is fixed in 6.18. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of drupal/drupal are affected by CVE-2010-3094? drupal/drupal (composer) versions >= 6.0, < 6.18 is affected.
Is there a fix for CVE-2010-3094? Yes. CVE-2010-3094 is fixed in 6.18. Upgrade to this version or later.
Is CVE-2010-3094 exploitable, and should I be worried? Whether CVE-2010-3094 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-2010-3094 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-2010-3094? Upgrade drupal/drupal to 6.18 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)