What is GHSA-G5VJ-WJ9X-4JG9?

GHSA-G5VJ-WJ9X-4JG9 is a medium-severity cross-site scripting (XSS) vulnerability in symbiote/silverstripe-multivaluefield (composer), affecting versions >= 3.0.0, < 3.1.0. It is fixed in 3.1.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is GHSA-G5VJ-WJ9X-4JG9?

GHSA-G5VJ-WJ9X-4JG9 has a CVSS score of 6.1 (Medium). 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 symbiote/silverstripe-multivaluefield are affected by GHSA-G5VJ-WJ9X-4JG9?

symbiote/silverstripe-multivaluefield (composer) versions >= 3.0.0, < 3.1.0 is affected.

Is there a fix for GHSA-G5VJ-WJ9X-4JG9?

Yes. GHSA-G5VJ-WJ9X-4JG9 is fixed in 3.1.0. Upgrade to this version or later.

Is GHSA-G5VJ-WJ9X-4JG9 exploitable, and should I be worried?

Whether GHSA-G5VJ-WJ9X-4JG9 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 GHSA-G5VJ-WJ9X-4JG9 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.

GHSA-G5VJ-WJ9X-4JG9

Q: How severe is GHSA-G5VJ-WJ9X-4JG9?

GHSA-G5VJ-WJ9X-4JG9 has a CVSS score of 6.1 (Medium). 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 symbiote/silverstripe-multivaluefield are affected by GHSA-G5VJ-WJ9X-4JG9?

symbiote/silverstripe-multivaluefield (composer) versions >= 3.0.0, < 3.1.0 is affected.

Q: Is there a fix for GHSA-G5VJ-WJ9X-4JG9?

Yes. GHSA-G5VJ-WJ9X-4JG9 is fixed in 3.1.0. Upgrade to this version or later.

Q: Is GHSA-G5VJ-WJ9X-4JG9 exploitable, and should I be worried?

Whether GHSA-G5VJ-WJ9X-4JG9 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 GHSA-G5VJ-WJ9X-4JG9 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 GHSA-G5VJ-WJ9X-4JG9?

Upgrade symbiote/silverstripe-multivaluefield to 3.1.0 or later.

Summary

symbiote/silverstripe-multivaluefield Possible PHP Object Injection via Multi-Value Field Extension

A potential deserialisation vulnerability has been identified in the symbiote/silverstripe-multivaluefield which could allow an attacker to exploit implementations of this module via object injection.

Support for handling PHP objects as values in this module has been deprecated, and the serialisation technique has been switched to using JSON for handling arrays.

As well as this, a potential XSS (cross-site scripting) vulnerability has been identified and remediated.

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.

GHSA-G5VJ-WJ9X-4JG9 has a CVSS score of 6.1 (Medium). 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 (3.1.0); upgrading removes the vulnerable code path.

Affected versions

symbiote/silverstripe-multivaluefield (>= 3.0.0, < 3.1.0)

Security releases

symbiote/silverstripe-multivaluefield → 3.1.0 (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 symbiote/silverstripe-multivaluefield to 3.1.0 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 GHSA-G5VJ-WJ9X-4JG9? GHSA-G5VJ-WJ9X-4JG9 is a medium-severity cross-site scripting (XSS) vulnerability in symbiote/silverstripe-multivaluefield (composer), affecting versions >= 3.0.0, < 3.1.0. It is fixed in 3.1.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is GHSA-G5VJ-WJ9X-4JG9? GHSA-G5VJ-WJ9X-4JG9 has a CVSS score of 6.1 (Medium). 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 symbiote/silverstripe-multivaluefield are affected by GHSA-G5VJ-WJ9X-4JG9? symbiote/silverstripe-multivaluefield (composer) versions >= 3.0.0, < 3.1.0 is affected.
Is there a fix for GHSA-G5VJ-WJ9X-4JG9? Yes. GHSA-G5VJ-WJ9X-4JG9 is fixed in 3.1.0. Upgrade to this version or later.
Is GHSA-G5VJ-WJ9X-4JG9 exploitable, and should I be worried? Whether GHSA-G5VJ-WJ9X-4JG9 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 GHSA-G5VJ-WJ9X-4JG9 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 GHSA-G5VJ-WJ9X-4JG9? Upgrade symbiote/silverstripe-multivaluefield to 3.1.0 or later.