How severe is GHSA-g5vj-wj9x-4jg9?

GHSA-g5vj-wj9x-4jg9 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g5vj-wj9x-4jg9?

GHSA-g5vj-wj9x-4jg9 affects the following packages: symbiote/silverstripe-multivaluefield (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-g5vj-wj9x-4jg9?

Update symbiote/silverstripe-multivaluefield to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5vj-wj9x-4jg9 is resolved across your whole dependency graph.

How do I detect GHSA-g5vj-wj9x-4jg9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symbiote/silverstripe-multivaluefield, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g5vj-wj9x-4jg9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g5vj-wj9x-4jg9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g5vj-wj9x-4jg9 can be triaged on real exposure rather than presence alone.

Is GHSA-g5vj-wj9x-4jg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g5vj-wj9x-4jg9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g5vj-wj9x-4jg9 published, and has it been updated?

GHSA-g5vj-wj9x-4jg9 was published on May 29, 2024 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

GHSA-g5vj-wj9x-4jg9 — symbiote/silverstripe-mul…

MEDIUMFix: symbiote/silverstripe-multivaluefield@31fbc8c

GHSA-g5vj-wj9x-4jg9 is a medium-severity (CVSS 6.1) remote code execution vulnerability in symbiote/silverstripe-multivaluefield. A fix is available for symbiote/silverstripe-multivaluefield — see the affected versions and patch details below.

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

Published

May 29, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘symbiote/silverstripe-multivaluefield

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symbiote/silverstripe-multivaluefield`	≥ 3.0.0&&< 3.1.0	3.1.0`composer require symbiote/silverstripe-multivaluefield:^3.1.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symbiote/silverstripe-multivaluefield, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symbiote/silverstripe-multivaluefield to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g5vj-wj9x-4jg9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g5vj-wj9x-4jg9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g5vj-wj9x-4jg9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-g5vj-wj9x-4jg9 in your dependencies?

O3 Security finds GHSA-g5vj-wj9x-4jg9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works