What is CVE-2022-30120?

CVE-2022-30120 is a low-severity cross-site scripting (XSS) vulnerability in concrete5/core (composer), affecting versions >= 9.0.0, < 9.1.0. It is fixed in 9.1.0, 8.5.8. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2022-30120?

CVE-2022-30120 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of concrete5/core are affected by CVE-2022-30120?

concrete5/core (composer) versions >= 9.0.0, < 9.1.0 is affected.

Is there a fix for CVE-2022-30120?

Yes. CVE-2022-30120 is fixed in 9.1.0, 8.5.8. Upgrade to this version or later.

Is CVE-2022-30120 exploitable, and should I be worried?

Whether CVE-2022-30120 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-2022-30120 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-2022-30120 in concrete5/core

Q: How severe is CVE-2022-30120?

CVE-2022-30120 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of concrete5/core are affected by CVE-2022-30120?

concrete5/core (composer) versions >= 9.0.0, < 9.1.0 is affected.

Q: Is there a fix for CVE-2022-30120?

Yes. CVE-2022-30120 is fixed in 9.1.0, 8.5.8. Upgrade to this version or later.

Q: Is CVE-2022-30120 exploitable, and should I be worried?

Whether CVE-2022-30120 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-2022-30120 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-2022-30120?

Upgrade: concrete5/core to 9.1.0 or later, concrete5/core to 8.5.8 or later.

Summary

Cross site scripting in Concrete CMS

XSS in /dashboard/blocks/stacks/view_details/ - old browsers only. When using an older browser with built-in XSS protection disabled, insufficient sanitation where built urls are outputted can be exploited for Concrete 8.5.7 and below as well as Concrete 9.0 through 9.0.2 to allow XSS. This cannot be exploited in modern-day web browsers due to an automatic input escape mechanism. Concrete CMS Security team ranked this vulnerability 3.1with CVSS v3.1 Vector AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N. Sanitation has been added where built urls are output.

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.

CVE-2022-30120 has a CVSS score of 3.1 (Low). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.1.0, 8.5.8); upgrading removes the vulnerable code path.

Affected versions

concrete5/core (>= 9.0.0, < 9.1.0) concrete5/core (< 8.5.8)

Security releases

concrete5/core → 9.1.0 (composer) concrete5/core → 8.5.8 (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 the following packages to resolve this vulnerability:

concrete5/core to 9.1.0 or later; concrete5/core to 8.5.8 or later

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

Frequently Asked Questions

What is CVE-2022-30120? CVE-2022-30120 is a low-severity cross-site scripting (XSS) vulnerability in concrete5/core (composer), affecting versions >= 9.0.0, < 9.1.0. It is fixed in 9.1.0, 8.5.8. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2022-30120? CVE-2022-30120 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of concrete5/core are affected by CVE-2022-30120? concrete5/core (composer) versions >= 9.0.0, < 9.1.0 is affected.
Is there a fix for CVE-2022-30120? Yes. CVE-2022-30120 is fixed in 9.1.0, 8.5.8. Upgrade to this version or later.
Is CVE-2022-30120 exploitable, and should I be worried? Whether CVE-2022-30120 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-2022-30120 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-2022-30120?
- Upgrade concrete5/core to 9.1.0 or later
- Upgrade concrete5/core to 8.5.8 or later

Other vulnerabilities in concrete5/core

CVE-IDSeverityPackage summary

CVE-2022-30117Criticalconcrete5/core: Path traversal in Concrete CMS CVE-2022-21829Highconcrete5/core: Code injection in concrete CMS CVE-2021-22970Mediumconcrete5/core: Server-Side Request Forgery in Concrete CMS CVE-2021-22969Mediumconcrete5/core: Server-Side Request Forgery in Concrete CMS CVE-2021-22951Mediumconcrete5/core: Password exposure in concrete5/core