Skip to content

Potential Gadget Chain allowing Remote Code Execution

Low
alexander-schranz published GHSA-x3c7-22c8-prg7 Jun 13, 2025

Package

composer handcraftedinthealps/goodby-csv (Composer)

Affected versions

<=1.4.2

Patched versions

1.4.3

Description

Impact

goodby-csv could be used as part of a chain of methods that is exploitable when an insecure deserialization vulnerability exists in an application. This so-called "gadget chain" presents no direct threat but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

Patches

Has the problem been patched? What versions should users upgrade to?

The problem is patched with Version 1.4.3

Workarounds

Patch src/Goodby/CSV/Export/Standard/Collection /CallbackCollection.php:

+    public function __wakeup() {
+       throw new \BadMethodCallException('Cannot unserialize ' . __CLASS__);
+    }

However, this is not directly exploitable; a separate vulnerability must be present to allow an attacker to pass unsafe input to unserialize(). There are no such known exploits in goodby-csv.

References

Are there any links users can visit to find out more?

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

CVE ID

CVE-2025-49597

Weaknesses

Credits